There is a better workaround: get the code from the .dump command of sqlite3 utility and use it... it creates a fresh copy of your database like using
sqlite3 dbold .dump | sqlite3 newdb (not sure about the syntax, there´s a example of this case on internet) -----Original Message----- From: Ronny Dierckx [mailto:[EMAIL PROTECTED] Sent: quarta-feira, 10 de outubro de 2007 13:55 To: sqlite-users@sqlite.org Subject: Re: [sqlite] how to get file handle from sqlite3 object? I think a possible solution is to lock the database with a "BEGIN EXCLUSIVE" statement and then copy the database file. ----- Original Message ----- From: "Cyrus Durgin" <[EMAIL PROTECTED]> To: <sqlite-users@sqlite.org> Sent: Wednesday, October 10, 2007 6:41 PM Subject: Re: [sqlite] how to get file handle from sqlite3 object? > Agreed - it seems like this would be useful enough functionality that I'm > not sure everyone who needs it should be reinventing the wheel... > > So is it fair to say that the sqlite3_file API methods are not useful for > this purpose? The docs are a bit sparse regarding their intended > purposes. > > On 10/10/07, John Stanton <[EMAIL PROTECTED]> wrote: >> >> There is a good case to have an Sqlite API call to take a snapshot of a >> database. It would integrate with the locking logic and secure an >> exclusive lock before taking the snapshot. That is a safer and handier >> approach than extracting a file descriptor and perhaps creating mayhem. >> >> Cyrus Durgin wrote: >> > Maybe it would help to state my use case: without this functionality, >> what >> > is the proper way to copy a database using the C API without >> > introducing >> a >> > race condition? >> > >> > On 10/9/07, Robert Simpson <[EMAIL PROTECTED]> wrote: >> > ---------------------------------------------------------------------------- - To unsubscribe, send email to [EMAIL PROTECTED] ---------------------------------------------------------------------------- - ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
