On 13 Sep 2014, at 1:21am, Richard Hipp <d...@sqlite.org> wrote: > On Fri, Sep 12, 2014 at 8:07 PM, Simon Slavin <slav...@bigfraud.org> wrote: > >> one thing that annoys me about SQLite is that it needs to make a >> journal file which isn't part of the database file. Why ? Why can't it >> just write the journal to the database file it already has open ? This >> would reduce the problems where the OS prevents an application from >> creating a new file because of permissions or sandboxing. > > Where in the database does the journal information get stored?
Good points, all of them. I don't doubt that the dev team has considered all these things carefully and chosen the best solution for the circumstances. > There are also performance reasons for separating the temporary tables and > indexes. Because temporary tables do not have to be preserved across a > system crash, SQLite is able to take lots of short-cuts when writing > temporary tables (for example: omitting fsync() calls) which make them run > must faster. I never thought of either of those points. Just goes to show. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
