Comment Comment by nailk > MySQL's traditional "fast" table type doesn't support transactionsInnoDB is the traditional table type now. Myisam was forgotten long time ago.> we had to set up our own custom collation to get, for example, "e" and "é" to be considered distinct charactersYou could just use "varchar CHARACTER SET utf8 COLLATE utf8_bin"> MySQL infamously accepted almost any kind of garbage values regardless of declared column typeThere is a setting that allows strict checking.> I cannot at this point imagine using MySQL for any kind of serious project.It is used by many for serious projects. parent nailk 9 years ago
InnoDB is the traditional table type now. Myisam was forgotten long time ago.
> we had to set up our own custom collation to get, for example, "e" and "é" to be considered distinct characters
You could just use "varchar CHARACTER SET utf8 COLLATE utf8_bin"
> MySQL infamously accepted almost any kind of garbage values regardless of declared column type
There is a setting that allows strict checking.
> I cannot at this point imagine using MySQL for any kind of serious project.
It is used by many for serious projects.