Regarding: ... my criteria for a lean and slim SQlite3 db access ... I can use in my DVD-ROM project.
I don't know for sure, but I'd suspect that any time saved by using prepared statements would be vastly overwhelmed by even one extra DVD-rom seek. I imagine you VACUUM the database before burning it to disk, right? Setting as large a cache size as practical might help to keep some indices in RAM. If by chance this is reasonable for your application, you could even copy some tables to a database in temporary space on the target system's hard drive, and ATTACH this db to your DVD-rom DB. If there are some long strings (or blobs) in the database, then it may help to define key columns first, and put the lengthier columns last -- or in their own separate tables. Even if you have plenty of space on the DVD rom, there might even been a performance improvement by using a compressed file system so as to reduce seeks. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
