> SQLite seeks to keep its database file size minimized. > I think that SQLite should by default continue to follow > its current strategy of minimizing file size. But I > am not adverse to adding a PRAGMA that will put the > database into a different "preallocation" mode where > the database size increases by larger chunks. At the > time of each size inceased, the additional unused space > can simply be added to the freelist. There are a few > unused bytes in the database file header that can be > used to record the fact that the "preallocation" pragma > is in force, so no file format change of any kind is > required - older versions of SQLite would continue to > be able to read and write newer databases.
> This is something we may look into over the next > few months > -- > D. Richard Hipp <[EMAIL PROTECTED]> That looks promising. Because SQLite is very good to manage freelists, so such type of preallocation will require to add some more chunk to freelist in SQLite DB file. And app developers who can estimate how SQLite DB file size will be increasing will be able to reduce fragmentation to get improved SQLite performance. (In many cases, end-users of app may not have even idea which database their app is using, where and how app is storing data. So app developers may use such feature for performance improvement) Rohit -- View this message in context: http://www.nabble.com/Avoiding-Fragmentation-of-SQLite-database-file-----t1780629.html#a4871149 Sent from the SQLite forum at Nabble.com.
