On 04/14/11 11:30, Calle Dybedahl wrote:
For the past 6-7 years, I've worked as a consultant in a lot of development
projects, nearly all of which involved MySQL for historical reasons. My role in
the projects have varied, from architect to troubleshooter. My opinion, based
on long and painful experience, is that MySQL technically is a *horrible*
choice. If you care about keeping your data consistent, do not use it. You can
never rely on MySQL honoring constraints, so you have to do all your data
integrity checking in the application. As a trivial demonstration, create a
table with a NOT NULL Text column and then insert an empty row. MySQL will
happily do as you say, putting an empty string in the Text column. It is
possible to bludgeon MySQL into nearly being reliable, but it's not the default
behavior and it will vanish at the slightest mistake.
I do agree 100%. The SQL wrapper around grep remains an SQL wrapper
around grep. With tons of bells and whistles.
Alex.
_______________________________________________
List: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/dbix-class
IRC: irc.perl.org#dbix-class
SVN: http://dev.catalyst.perl.org/repos/bast/DBIx-Class/
Searchable Archive: http://www.grokbase.com/group/[email protected]
