On 7/29/18, Jürgen Palm wrote:
> As a quick, ugly workaround for my situation I could add something like
>sqlite3_exec(conn1, "SELECT 1",NULL,NULL,NULL);
> before the sqlite3_prepare_v2 after the schema change.
>
> Is there any better way? Or would it be possible to add a SQLITE_PREPARE
>
Richard Hipp wrote:
On 7/29/18, Jürgen Palm wrote:
Hi,
in an application I encountered a problem, where the changing of the
structure of a table by dropping and recreating it via one connection to
a db was not directly seen by another connection to the same db.
Detecting a schema change
On 7/29/18, Jürgen Palm wrote:
> Hi,
>
> in an application I encountered a problem, where the changing of the
> structure of a table by dropping and recreating it via one connection to
> a db was not directly seen by another connection to the same db.
Detecting a schema change requires starting
3 matches
Mail list logo
