×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Thursday, August 09, 2007 11:31 AM
To: midrange-l@xxxxxxxxxxxx
Subject: SQL rewrite
Contrary to some listers opinions that SQL should only be
used for set-at-a-time logic, and that the existence of a
cursor is proof that you're doing something wrong,
Hey, I think I resemble that remark ;-)
But I never said cursors are _always_ wrong, I just said that they often are.
Beside, bet I could get the runtime down to 30 seconds without a cursor <grin>
Seriously though, the motto I share with SQL newbies is "If you're using a cursor, you're probably
doing something wrong." I think its particularly helpful to SQL newbies who are used to RLA and thus
their first thought is "I need a cursor...to read one record at a time."
Experienced SQL developers on the other hand should be able to tell when a cursor is the best or only
way to accomplish something.
Charles
This e-mail transmission contains information that is intended to be confidential and privileged. If you receive this e-mail and you are not a named addressee you are hereby notified that you are not authorized to read, print, retain, copy or disseminate this communication without the consent of the sender and that doing so is prohibited and may be unlawful. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please delete and otherwise erase it and any attachments from your computer system. Your assistance in correcting this error is appreciated.
midrange.com
