On Sat, Mar 12, 2005 at 10:03:25AM -0700, Ara.T.Howard wrote: > does anyone have a strategy for doing massive updates to a db and atomicly > replacing it in a multi-process situation?
Why would you want to do that? SQLite properly supports transactions, so aren't you better of just using those? What scenario are you working with here? Do you have a large number of readers that MUST not block while a massive/slow update is done tot he database, or something like that? -- Andrew Piskorski <[EMAIL PROTECTED]> http://www.piskorski.com/
