Sqlite maintains its data in a disk file. It only reads and writes to that file sufficient bytes to maintain changes to the database or to satisfy the query. It uses memory to cache data while it processes it and will write changed parts of that data back to the disk file.
Fundamentally Sqlite organizes data as "pages", fixed size chunks of the disk file. It reads pages and writes back altered or freshly created ones. [EMAIL PROTECTED] wrote: > I understand that the SQLite database resides in memory. I understand that > the information in memory gets written to disk, ie saving parts that have > been updated/whole database. > > I have read that SQLite has been known to support up 100,000 concurrent > read connections and can support several terabytes of data. > > Now lets say a database is 10Gb in size and it is written to disk. Would > not writing a 10Gb file to disk take a very long time? > > Now perhaps SQLite can just write the part that has changed to disk. > > If this is the case, then how does it know which sectors on the hard drive > to update since it isn't writing the entire file to disk > > Can someone explain to me how all of this work? > > Thanks, > TD > > -------------------------------------------------------------------- > mail2web.com - Microsoft® Exchange solutions from a leading provider - > http://link.mail2web.com/Business/Exchange > > > _______________________________________________ > 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
