We run Sybase at work for our in-house apps. But, if your application does not
need to do "fancy" transactions or stored procedures than MySQL is my choice. The
speed blows Sybase away because it doesn't have all that "overhead".
John Aldrich wrote:
> On Mon, 01 Nov 1999, you wrote:
> > On Mon, Nov 01, 1999 at 02:40:03PM -0500, Damien Mc Kenna wrote:
> > > For doing a pretty large databased web site for a college department
> > > (with all the cool stuff in PHP), which would people recommend I use:
> > > PostreSQL or MySQL? I've noticed that a lot of the PHP packages I'm
> > > looking at seem to favor MySQL, but PostgreSQL is getting more support
> > > these days. Should I just read through their respective documentations
> > > and figure it out for myself, or does anyone have a recommendation, or
> > > are there any good comparisons of them on the net?
> >
> > I'm rather partial to MySQL, but only because it seemed easier to deal with
> > to me. PostgreSQL seems to do alot of things _outside_ the database, rather
> > than dealing with them inside normal tables.
> >
> > Some of the decision will depend on what sorts of things you need to do
> > with the database. I know that MySQL doesn't handle straight transactions,
> > nor can it do table or row locking. I don't recall whether PostgreSQL
> > handles those normally.
> >
> > I do know there was a rather lengthy discussion about this very topic on
> > Slashdot awhile ago. You might try there. http://slashdot.org
> >
> Try Sybase... :-) It rocks!!! At the ISP where I work, we are hosting
> the FIRST authorized electronic check conversion system (authorized
> by the Feds and by the banking industry!) and it has a HUGE database,
> and is being run off a couple Sybase servers. :-)
> John
