Kevin Dangoor wrote:
For the record, I'm a big fan of foreign key constraints, and I always
use InnoDB tables when I use MySQL.
I'm quite glad to hear that. Of course I've been working under the
assumption that this was the case, but of course didn't know for sure.
I mean, it isn't like MySQL *can't* support data integrity (although
it's still not ACID and probably never will be), but most MySQL guys
have been brainwashed into thinking that because MySQL can't do it you
shouldn't do it (and the MySQL devs themselves openly encouraged this
attitude). Worse, most of them have developed bad habits that they are
disinclined to reform, so even as MySQL has grown, they haven't. You
could buy them all perpetual Oracle licenses and they'd still fail to
use any sort of referential integrity checks.
Stored procedures is the place
where I'm likely to draw the line (but i do know that there are places
where even stored procedures make good sense).
Yes, that is an arguable area and one that I could probably let pass or
even be convinced of. I use them when they make sense, but they are
enough of a pain to just to edit, let alone maintain that even if I
think they *might* make sense I'm still inclined to not use them ;-)
One day I'll get my FUSE plugin for directly editing PostgreSQL
procedures done and we'll see how I feel then ;-)
Cliff
