>Stored procedures aren't really needed for Sqlite, since the program you write around Sqlite can certainly implement any 'stored' procedures itself. True. However in a multi-language environment (say Python, C, PHP) that would mean implementing all 'stored' procedures multiple times. And of course it will not be a question *IF* these implementations will be out of sync one day but *WHEN* - with potentially fatal results for your data. The same goes for Triggers - easy to implement in application code. And who needs things like *Foreign Keys* - it is not as if that could not be implemented in an application. (That was sarcasm - sorry). There is a lot of functionality in SQLite that not *everyone* needs or uses. A lot of people will never use FTS (I do), others will never need Geopoly (I don't).