Actually, no, it's not. In the strictest possible mode, employing
every single way to ensure your data is consistent and that foreign
keys are being honored, there's a simple thing anyone can do to screw
you with MySQL.
SET FOREIGN KEYS OFF;
Oh, you mean that, if you turn checking off, it doesn't do checking?
Gasp! Why, that's like saying that a gun fires bullets when you pull
the trigger. So just don't set foreign keys off. Foreign keys is on by
default.
BAM! You're done. Finished. You cannot trust a single thing in your
database the way you can in EVERY SINGLE OTHER relational database.
Well, why did you turn off checking? It's a TOOL, a powerful tool. Like all
powerful tools, if you disabled the safeties, you have to know what you're
doing. Just like a power saw, you can do very good work, or you can cut off your
thumb.
Screaming the tool is unsafe because you can disable the safeties which are on
by default is akin to crying for your nanny to cool your milk so you don't get
burned
by the hot hot hot cup.
_______________________________________________
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]
