Just some observations after reading mail on this forum.
It is wise when using Sqlite to design your database and application to work to the strengths, not weaknesses of Sqlite. Be aware that Sqlite only uses one index per table in a query and that it's cache is tied to a connection. If you observe those constraints you get a good result - an easy to implement and maintain database with a snappy performance
If you have a legacy application which violates those constraints or an envisaged application which cannot comply, then you should look to using something like PostgreSQL. When you need a big hammer, don't pick up a Lite one.
----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
