From: | "Adam Lang" <aalang(at)rutgersinsurance(dot)com> |
---|---|
To: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Why PostgreSQL is not that popular as MySQL? |
Date: | 2000-12-05 15:48:13 |
Message-ID: | 007701c05ed2$c6aacf80$330a0a0a@6014cwpza006 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
As for me, when I was trying to decide and not as aware of the significance
of certain functionality's, I almost went with MySQL for a simple reason.
90% of the code examples I found involved MySQL as oppsoed to Postgresql.
That also implies it will be easier to find general help for MySQL than
Postgresql.
Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
http://www.rutgersinsurance.com
----- Original Message -----
From: "Mike Castle" <dalgoda(at)ix(dot)netcom(dot)com>
To: <pgsql-general(at)postgresql(dot)org>
Sent: Monday, December 04, 2000 6:41 PM
Subject: Re: [GENERAL] Why PostgreSQL is not that popular as MySQL?
> On Mon, Dec 04, 2000 at 03:05:23PM -0800, Dan Lyke wrote:
> > I've been seriously programming microcomputers for a decade and a
> > half. One of the great accomplishments of my career was shoehorning a
> > big database application into a 4.77 MHz PC XT under that 640k limit,
> > including the bigger versions of DOS and the Novell drivers. 30 meg
> > was a *huge* database. Assembly language and special case hacks to
> > CTREE (which we only used part of because the record management was
> > more inefficient than we could tolerate) were the norm.
>
> This is interesting.
>
> I too come from a background of using CTREE (I'm assuming you mean the
> product from www.faircom.com)
>
> And this exposure was precisely why I choose Postgres over MySQL.
> Maybe because I switched over later and started using transactions once
> CTREE supported them (prior to that, we literally made backup copies of
> the files to simulate transactions!).
>
> I too am used to putting all of the integrity issues into the application.
> And many many times I'd come close to writing a layer on top of ctree that
> did exactly that! But having started using PostgresQL, I am hooked on
> having the database handle it. Constantly reinventing the wheel inside
the
> application is annoying! And not very exciting.
>
> mrc
> --
> Mike Castle Life is like a clock: You can work constantly
> dalgoda(at)ix(dot)netcom(dot)com and be right all the time, or not work at all
> www.netcom.com/~dalgoda/ and be right at least twice a day. -- mrc
> We are all of us living in the shadow of Manhattan. -- Watchmen
From | Date | Subject | |
---|---|---|---|
Next Message | hubert depesz lubaczewski | 2000-12-05 16:04:03 | strange memory-consumming psql ... |
Previous Message | mwaples | 2000-12-05 15:26:46 | looking for more PL/PGsql examples |