On 16 Oct 2010, at 9:07pm, Chris Percol wrote: > I am thinking of moving from mysql to sqlite3 and want to know if there are > any gotchas?
The numbers you mention don't suggest problems. Consider your indexes carefully. MySQL makes up temporary indexes cleverly if you don't declare appropriate ones, and it maintains them until the server process quits [1]. Consequently failing to declare any indexes at all does very little harm. SQLite3 has no server process, makes up temporary indexes for each separate command, and destroys them afterwards. So failure to make appropriate indexes causes it to be very slow. Simon. [1] complicated handwaving here _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users