Andrew Shakinovsky wrote:
Thanks. That works great. I would agree with Dennis that this
functionality should belong in the API, however, after reading the
following post, I can see why it is not done this way:
http://www.mail-archive.com/sqlite-users@sqlite.org/msg11398.html
Andrew,
The
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Saturday, April 01, 2006 7:08 AM
> To: sqlite-users@sqlite.org
> Subject: Re: [sqlite] Question regarding schema change error ...
> It is easy to put wrappers around sqlite3_prepare(), sqli
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Saturday, April 01, 2006 7:08 AM
> To: sqlite-users@sqlite.org
> Subject: Re: [sqlite] Question regarding schema change error
> ...
> It is easy to put wrappers around sqlite3_prepa
[EMAIL PROTECTED] wrote:
"Andrew Shakinovsky" <[EMAIL PROTECTED]> wrote:
According to the docs, I am asked to finalize the
statement [after SQLITE_SCHEMA], and re-prepare it. Unfortunately
this doesn't fit nicely into my architecture.
It is easy to put wrappers around sqlite3_prepare
"Andrew Shakinovsky" <[EMAIL PROTECTED]> wrote:
> According to the docs, I am asked to finalize the
> statement [after SQLITE_SCHEMA], and re-prepare it. Unfortunately
> this doesn't fit nicely into my architecture.
It is easy to put wrappers around sqlite3_prepare(),
sqlite3_step(), and sqlite3_
I am having a minor issue with schema changes and am looking for the
best solution/workaround. I am using the latest released version of
Sqlite, by the way.
I have a database which needs to be accessed by multiple
users/processes. During it's lifetime it will have tables added to it
periodically
6 matches
Mail list logo
