Darren Duncan wrote: > MySQL should be avoided like the plague. I hereby retract my above-quoted statement as I realize that it is too severe a statement to be making.
Instead I will say the following in its place: MySQL should not be considered as the default choice of a non-lite SQL DBMS, for projects not currently using it, when you have a choice between multiple SQL DBMSs; instead, the default non-lite choice should be Postgres. If you don't know the difference, then Postgres will serve you much better and keep you safer. Just choose MySQL if you are informed enough about various SQL DBMSs and can thereby justify that MySQL will actually serve your needs better. One reason for this is that Postgres defaults to more safer behaviors, while with MySQL you have to explicitly ask for some of the same safety nets, and people less knowledgeable about it won't know to do this. I will also say that for business-level use, it is no justification to say that MySQL is your only choice because that is the only thing the web host provides. If you're a serious business user, you have a lot more leverage to pick and choose any choice of software you want. > Use Postgres instead if you have to > switch to a larger SQL DBMS. But hopefully the help you've gotten so far > will > extend your mileage with SQLite and you won't have to switch to anything yet. See also my prior reply, about CHECK having never been fixed/supported in MySQL. -- Darren Duncan _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
