From: | "Rick Gigger" <rick(at)alpinenetworking(dot)com> |
---|---|
To: | "bob parker" <bob_parker(at)dodo(dot)com(dot)au>, "John Wells" <jb(at)sourceillustrated(dot)com>, <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Humor me: Postgresql vs. MySql (esp. licensing) |
Date: | 2003-10-10 18:54:43 |
Message-ID: | 003501c38f5f$f8f22630$0700a8c0@trogdor |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
My experience with mysql and postgres was this. I had some apps that were
running on SQL Server and I wanted to get rid of it because it was
expensive. Didn't really do much for us that the others couldn't, and I
wanted to get rid of windows. Plus administratively SQL Server just seemed
to have a lot more weird problems than the other two. So I started porting
one of my apps simultaneously to both postgres and mysql. I got to a part
of my app that used unions. At that time mysql didn't support unions (I
realize that it does now). I was absolutely amazed. Needless to say I
dropped mysql right there and have used nothing but postgres ever since.
The learning curve was maybe a tiny, tiny bit steeper than mysql but that is
just because postgres tends to do things right and then make them simple
(for example having sequences and then adding the serial key word) whereas
mysql just makes them simple. Once I started figuring things out though I
lost any desire to ever look at mysql again because there were so many areas
where postgres excelled and mysql lacked.
crg
----- Original Message -----
From: "bob parker" <bob_parker(at)dodo(dot)com(dot)au>
To: "John Wells" <jb(at)sourceillustrated(dot)com>; <pgsql-general(at)postgresql(dot)org>
Sent: Thursday, October 09, 2003 5:12 PM
Subject: Re: [GENERAL] Humor me: Postgresql vs. MySql (esp. licensing)
> On Thu, 9 Oct 2003 01:28, John Wells wrote:
> > Yes, I know you've seen the above subject before, so please be gentle
with
> > the flamethrowers.
> >
> > I'm preparing to enter a discussion with management at my company
> > regarding going forward as either a MySql shop or a Postgresql shop.
> >
> > It's my opinion that we should be using PG, because of the full ACID
> > support, and the license involved. A consultant my company hired before
> > bringing me in is pushing hard for MySql, citing speed and community
> > support, as well as ACID support.
>
> Apologies for the empty reply - my mind is on brain death so I needed to
> imitate it.
>
> I'll address only the alleged community support for MySql because you will
> get much better qualified replies to your other concerns from others.
>
> About 18 months ago I had to choose a DB for my home grown small systems.
> Knowing very little about them I lurked on the both this list and a MySql
> list for a couple of months.
>
> In contrast to this list, the MySql one not only had a high proportion of
> brain dead questions, there were a fair few answers of the same grade too.
>
> I quickly decided that Postgresql was the better product by far for that
and
> many other reasons.
>
> HTH
> Bob
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas LeBlanc | 2003-10-10 18:59:38 | Unique Index vs. Unique Constraint |
Previous Message | CSN | 2003-10-10 18:37:14 | Re: int1? types? |