If you could set the journcal location BEFORE you open the database that
wouldn't be such a bad thing. Giving us the ability to do this would allow for
the flexibility when needed with appropriate warnings about how to recover.
In particular, if you only access the database through your own application
there shouldn't be a problem. Only if you try to access the database with some
other "unaware" application.
Michael D. Black
Senior Scientist
Northrop Grumman Mission Systems
________________________________
From: sqlite-users-boun...@sqlite.org on behalf of Eric Smith
Sent: Wed 7/14/2010 11:24 AM
To: General Discussion of SQLite Database
Subject: EXTERNAL:Re: [sqlite] Sqlite Insert Speed Optimization
Black, Michael (IS) wrote:
> Does anybody know how to make the journal file go to a different
> location than the database? Apprarently it's not treated as a "temporary"
> file. Perhaps it should be??
Seems like you'd have to communicate the journal location to other
processes, meaning you'd have to write the name of the journal file
into the main db, in the header or something. I think sqlite doesn't
do that at the moment, which means you'd have to change the file
format, which sqlite devs are loath to do.
--
Eric A. Smith
Worthless.
-- Sir George Bidell Airy, KCB, MA, LLD, DCL, FRS, FRAS
(Astronomer Royal of Great Britain), estimating for the
Chancellor of the Exchequer the potential value of the
"analytical engine" invented by Charles Babbage, September
15, 1842.
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
