Well, now I am writing a proposal, which among many other points, proposes to switch from the current hosting site of a non profit to a slightly more expensive one running PostgreSQL, (where I have some other projects.) I want to use as my main argument, the fact (at this time, only from my previous usage), that MySQL really doesn't have foreign keys or record locking, and Postgres does.
I will be trusted to say this, and I don't have to reprint the manuals from each DB in my proposal, or maybe I will. But anyway, I'm still correct with today's MySQL vs. PostgreSQL, right? I *really* want to use PostgreSQL for this project and not MySQL as I want to avoid growing pains trying to get MySQL to do the job of a bigger DB down the road.
-- "You are behaving like a man", is an insult from some women, a compliment from an good woman.
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
