Michael Knigge <[EMAIL PROTECTED]> wrote:
> > THe bigger question is why you are designing a new system to
> > work with SQLite-2. SQLite-2 is in maintenance for use on legacy
>
> Eh... sorry, I was in a hurry of course I use sqlite3_finalize()!
>
>
> > systems. Use SQLite-3 instead.
THe bigger question is why you are designing a new system to
work with SQLite-2. SQLite-2 is in maintenance for use on legacy
Eh... sorry, I was in a hurry of course I use sqlite3_finalize()!
systems. Use SQLite-3 instead. sqlite3_finalize() cannot fail
for any reason other than
Michael Knigge <[EMAIL PROTECTED]> wrote:
> All,
>
> I wonder what I have to do if sqlite_finalize() fails? sqlite_close()
> will fail if there are any prepared statements associated with a
> database handle - so I can't close.
>
> Due to the manual, sqlite_finalize() could return SQLITE_ABORT
All,
I wonder what I have to do if sqlite_finalize() fails? sqlite_close()
will fail if there are any prepared statements associated with a
database handle - so I can't close.
Due to the manual, sqlite_finalize() could return SQLITE_ABORT - do I
have to call sqlite_finalize() again in this
4 matches
Mail list logo