> those items could be dealt with at the application later That was always one of the arguements, but beyond toy projects or at least beyond a single simple ap

> those items could be dealt with at the application later That was always one of the arguements, but beyond toy projects or at least beyond a single simple app accessing the DB the application layer is not the best place for that to be implemented. Maybe I'm anal, but there is a point where giving up correctness for performance feels far too icky to me. Also those professing mysql to be the solution back then did so with an almost religious furvour that is always troubling, and if something else threatened their messiah such as sqlite beating it in some benchmark by their own terms, ooh there were hissy-fits and claims of witchcraft!