Sqlite uses cacheing. I would suggest not storing large amounts of data in PHP arrays. It is buffer shadowing. Ideally with Sqlite you would use a cursor (the sqlite3_step logic) and pick up rows as you need them from the Sqlite cache.
Digging a string of holes and filling them in is a tedious way to move a hole in the ground Zbigniew Baniewski wrote: > On Mon, Feb 18, 2008 at 08:33:49AM -0800, Scott Baker wrote: > >> The less database hits you have to do, the faster your code will be. >> Getting all the data into a PHP data structure should be the way to go. > > But, if one really is "loading all the data into memory at once" (just > "SELECT * FROM xyz") - where are, actually, any benefits from using SQL > database engine? > > Using plain file you can have about the same: open/read_all/close... done. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
