hi, i had have a look, i may be able to use this. this will be in an embedded hardware application, so i don't have a command line, only what i code in.
i was hoping to do a binary copy of the db from a ram file system to flash memory for permanent storage. flash is really slow, so a copy would be a lot quicker than a series of .dump Inserts. which really requires sqlite running on a flash file system as well. a copy is really all i want, but knowing when everything is commited, or locking out other threads without them having to close the db. thanks, damian ________________________________ From: Mrs. Brisby [mailto:[EMAIL PROTECTED] Sent: Sun 1/05/2005 1:07 AM To: sqlite-users@sqlite.org Subject: Re: [sqlite] backup open database Why is it inappropriate to use: sqlite originaldb ".dump" | sqlite backupdb On Sun, 2005-05-01 at 00:28 +0800, Damian Slee wrote: > hi all, > i want to make a copy of a sqlite3 database file while it is open. is there > anyway that i can tell programatically that any caches/journals are flushed > out? or is there any way to get and exclusive lock i guess, before making a > backup copy? > > my proposed application would have quite a few threads which may have the > same sqlite db open for read or write (rarer), but i dont want to shut down > the application to definitely know it is safe to copy. > > > thanks, > > damian
