On Wed, 27 May 2015 19:07:50 +0200 Dominique Devienne <ddevienne at gmail.com> wrote:
> On Wed, May 27, 2015 at 6:59 PM, Wade, William <bill.wade at dnvgl.com> > wrote: > > > (including his own uuid, indicating that this is logically a new > > file). When existing readers get around to reading again, they will > > check that uuid, and handle the change in writers "gracefully." > > > > You can perhaps abuse the Application-Id [1] as your uuid to check. > But you could also store a real uuid in a 1-row well-known table. > Just a thought (on that specific point). --DD Better user-version pragma[2]. Application-Id identifies your sqlite3 db file with your application using unix file (1) program or similar. > [1] https://www.sqlite.org/pragma.html#pragma_application_id https://www.sqlite.org/pragma.html#pragma_schema_version If your new db has identical schema, don't modify the schema version. If you do so, readers must call sqlite3_reset() and sqlite3_prepare() again. --- --- Eduardo Morras <emorrasg at yahoo.es>
