I sometimes use SELECT ... with HOLD if I need to delete *a lot* of
rows from a table. DELETE ... WHERE ... grinds away for a while, then
aborts with Long Transaction. SELECT ... with HOLD, DELETE ... WHERE
CURRENT OF ..., and commit every 100 rows avoids that problem
Is there a better way ?
johnl@informix.com (Jonathan Leffler) wrote:
>I have seen a couple of answers, but neither of them addressed what I would
>regard as the fundamental question, which is:
>* If you aren't interested in the values from the SELECT, why are you using
> a SELECT FOR UPDATE and DELETE WHERE CURRENT OF statements?
<snip>