On Mon, 25 Jun 2007 18:38:30 +0000, D. Richard Hipp wrote: >"John Belli" <[EMAIL PROTECTED]> wrote: >> If the progress handler returns non-zero, sqlite_exec is returning >> SQLITE_INTERRUPT instead of SQLITE_ABORT. Was this intentional? The >> comment says SQLITE_ABORT, but the return is being set to >> SQLITE_INTERRUPT. >> (vdbe.c line 553) >> > >This change is part of the fix for the corruption bug in ticket #2409. >We didn't think anybody would notice. Is it causing problems for you?
Hah, no, not really. I just changed my code to look for either return value, so I can display the proper message. I was testing the return from a sqlite3_exec() for an error message display, and displaying a "canceled" message if it was SQLITE_ABORT. JAB -- John A. Belli Software Engineer Refrigerated Transport Electronics, Inc. http://www.rtelectronics.com ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
