> This yields two benefits: > > A less fragmented db > > ~50% vacuum speedup since the data is only copied once > > Currently we can copy the data to a new file, but it is a pretty > invasive change to swap all of the current sqlite connections to the new > file. Things like prepared statements, etc need to be updated for every > single db consumer. Thus it would make sense to have this feature on the > sqlite side. > > Is this reasonable request? > > Thanks, > Taras >
Taras, I once post similar observations and Jay A. Kreibich answered about the reasons why is implemented the way it is. You can read it here: http://www.mail-archive.com/sqlite-users@sqlite.org/msg50941.html Max _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
