At 00:48 19/03/2008, you wrote:
>Maybe this could be added as a "Feature request" to open_v2 ? > >Add, > >#define SQLITE_OPEN_OMIT_JOURNAL 0x00008000 > >Test this flag and set the omit_journal parameter to Btree >factory... To cause sqlite to omit journal creation. Obviously this >has serious impact to a databases recoverability. But when the >Durability component of ACID is not needed it should provide a nice >performance boost! Well you can do it. But keep in mind that it's your own modified version of sqlite. In ancient versions of sqlite, this works. Go to main.c and change the line: rc = sqlite3BtreeFactory(db, zFilename, 0, MAX_PAGES, &db->aDb[0].pBt); to rc = sqlite3BtreeFactory(db, zFilename, BTREE_OMIT_JOURNAL, MAX_PAGES, &db->aDb[0].pBt); and recompile. This way any file (database, temporal, virtualdb, etc..) sqlite creates will have no journal. Don't know if it works with 3.5.x but i think yes. Perhaps you should do other changes in sqlite code, don't know. >In my particular case, I have many small db files that have data. >These are "batched" into a db file. If the process fails the in >progress batch will simply be overwritten and re-created. Hence it >is an all or none approach and does not need any recoverability. Do you need to consult (search data in) the database? Or is it a "data-storage" file only? Perhaps you only need a temporal file for your app. >Thanks, >Ken HTH _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
