Re: Possible ODBC weirdness when deleting records

Delete triggers also cause a record by record deletion to occur.

Lastly, only need *CHG authority to the data to delete every record. You
have to have more authority than that to use CLRPFM or for SQL to delete
the data in one shot.

Charles

On Wed, Mar 9, 2016 at 4:26 PM, John Yeung <gallium.arsenide@xxxxxxxxx>
wrote:

On Wed, Mar 9, 2016 at 4:01 PM, Rob Berendt <rob@xxxxxxxxx> wrote:

lmgtfy delete from with no where clause acts like clrpfm

October 15th, 2013, 12:38 AM
A CLRPFM is executed when performing an SQL Delete Statement, if all rows
have to be deleted and there is no lock on the table/rows.

That certainly makes sense, but neither of my files had any locks on
them when I ran the script.

Oh, and I just confirmed the same behavior with STRSQL - one of the
files gets cleared but the other doesn't.

Hmm... just to further explore the lock thing - when I have the
clearable file open for viewing in some other program (on the i), my
script hangs when it tries to do the delete, as though it needs to
secure an exclusive lock before proceeding. When I have the other file
open (the one which does accumulate deleted records), my script can go
ahead and delete the records, even though I'm still viewing that file
in the other program.

So it would appear there is some kind of setting which *is* different
between those two files. And it would also appear that the "SQL will
perform CLRPFM if it can" doesn't work in my case. Or there is further
fine print on that matter.

John Y.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.