>"That is exactly my experience, and it leads not only to terrible databases but to piles of awful code written around terrible databases. " Not planning for t

>"That is exactly my experience, and it leads not only to terrible databases but to piles of awful code written around terrible databases. " Not planning for the future tends to do that. >"I am stuck with MySQL most of the time because I work with broken web applications, and so far all but a couple have used MySQL. As a long-time Oracle and SQL Server programmer I almost cry trying to figure out some of the MySQL databases I come actoss. I am working on one now that uses GUUIDs as primary keys in every table, generated in PHP code, for reasons I can only attribute to ignorance." Ouch, that sounds painful. I have horror stories I could tell too. Ambiguous foreign keys? ouch.....