There's more than one way to do things | |
PerlMonks |
Re^7: Conditional many to many relationships with Class::DBIby cbraga (Pilgrim) |
on Nov 02, 2004 at 15:36 UTC ( [id://404635]=note: print w/replies, xml ) | Need Help?? |
I never meant to flame, sorry.
When I mentioned MySQL changing data and ignoring the SQL standard I meant the kind of stuff pointed out here. I expected you to know abut that. For instance, if a column has a default value in Mysql, you can't insert a null value into it. If I attempt to do so Mysql will substitute the NULL for the column's default. And yes I know that's all fully documented, but it's still well documented wrong behaviour IMHO. Of course both Postgres and Oracle deviate from the SQL standard but Mysql does things that have no logical explanation. Another example: if a table has a timestamp column, that column (or the first timestamp if there's more than one) in each row is automatically updated every time the row is changed. How is that supposed to help me? How am I supposed to guess that that will happen when I create a timestamp I don't expect to be automatically updated? Why not name the datatype "autoupdate_timestamp" instead? And now Mysql is stuck with these wrong behaviours because they can't fix them without breaking compatibility with existing applications.
PostgreSQL does have replication and clustering solutions. Several, actually. I know of at least two that are open-source and free, though I've never tried them: ESC[78;89;13p ESC[110;121;13p
In Section
Seekers of Perl Wisdom
|
|