From: | "Andrew Snow" <andrew(at)modulus(dot)org> |
---|---|
To: | <pgsql-general(at)postgresql(dot)org> |
Subject: | RE: MySQL treads belong else where. |
Date: | 2001-08-30 11:20:02 |
Message-ID: | 000001c13145$b6ab7940$fa01b5ca@avon |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> So far I haven't seen any real flames or insults thrown about
> yet - no MYsql will kill your puppy threads at all. There
> can be rigourous discussion without insults being thrown and
> so far that's all I've seen.
No, but it WILL kill your data, if the DB is big enough and has been in
use long enough.. speaking from personal experience *weep* ;-)
I used to think mysql was great while I was learning SQL, because it was
free, unbloated, and easy to use. But I think one grows out of it for
larger and more complex projects... Postgres' larger set of features and
sophisticated locking become invaluable.
I know (from reading this list) that people sometimes have trouble with
PGSQL, but quite honestly I found that after I had read the Postgresql
docs in their entirety, everything "fit" and seemed intuitive. (I found
it not unlike the feeling of becoming a FreeBSD user after having used
linux...)
For the project as a whole I guess its a matter of killing off the
genuine FUD with one hand, and fixing the areas in Postgres that MySQL
does have genuinely have an advantage, with the other hand.
- Andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Tod McQuillin | 2001-08-30 12:34:24 | Re: sub select |
Previous Message | matthieuclavier | 2001-08-30 10:54:36 | Re: weird behaviour |