[Vince]

Quote:

Originally Posted by ZachKnoxx SQLite is my choice because there isn't a worry about query errors and of the such.

Wat. If anything, if you write wrong queries it will only be harder to debug because SQLite does not keep logs like the MySQL plugin does/can.

I also want to disprove Sergei's point about "not messing with threaded queries". If you have a moderately large database an extensive/expensive query can take a few seconds to complete. Doesn't seem like much, but if you don't thread then the main server process has to wait. This means no player updates, no callbacks being called, etc. This inevitably means that players will start to experience lag.

And my final point: the version of SQLite that is included with SA-MP doesn't seem to be have been updated since it was first implemented in 2007. This means it doesn't benefit of all the updates pushed since 2007 and it also means that it lacks a very basic feature: foreign key support. It is nearly impossible to build a properly normalized database without foreign key support. But then again, most SA-MP scripters don't know how to properly use them and can get away with merely 2 or 3 tables, whereas in both SA-MP projects I worked on I exceeded 50 tables both times.