× 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.


  1.  Home
  2. MIDRANGE-L
  3. March 2016

Re: Possible ODBC weirdness when deleting records

On Thu, Mar 10, 2016 at 11:25 AM, Vernon Hamberg
<vhamberg@xxxxxxxxxxxxxxx> wrote:
So an SQL DELETE might get around [the inability to perform CLRPFM] - and especially if one puts in a
WHERE 1 = 1.

Yes, and getting around the inability to perform CLRPFM is the whole
reason for the existence of this thread. (Though in my case it's not
an authority issue.)

Using that WHERE clause also gets rid of the annoying inquiry message that
you are deleting everything, do you really want to do this - that message
CAN halt things in a batch process, because there is no reply that is being
looked for.

Well, it's up to the "SQL client" whether or not attempting to delete
all the records deserves a warning. I've seen the message you're
talking about when I use STRSQL. But it is not a factor when issuing
SQL via ODBC.

John Y.

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.