Re: Re: LOCK TABLES using Perl in MySQL

How are PostgreSQL transactions more real than MySQL using the BerkeleyDB or InnoDB? I have to admit I'm not familiar with the differences, but I was under the impression that they were the same.

Also, I think some people might not agree that PostgreSQL is faster than MySQL. And how is it cheaper? They're both free!

I do agree that Postgres has more features though (missing subselects is almost unforgivable), but MySQL is catching up - apparently version 4.1 (which is scheduled to be out in a couple of months) will have subselects along with a load more features (secure connections! at last!).

Comment on Re: Re: LOCK TABLES using Perl in MySQL

Replies are listed 'Best First'.

Re: Re: Re: LOCK TABLES using Perl in MySQL
by merlyn (Sage) on Oct 13, 2001 at 19:42 UTC

How are PostgreSQL transactions more real than MySQL using the BerkeleyDB or InnoDB? I have to admit I'm not familiar with the differences, but I was under the impression that they were the same.

Also, I think some people might not agree that PostgreSQL is faster than MySQL.

And how is it cheaper? They're both free!

So let me say it this way. MySQL is fine for people who are moving up from DBM. But once you've played with Oracle, Pg is the way to go. You sacrifice far too much of "typical" database coding with MySQL. Maybe someday MySQL will have everything in SQL 92. But Pg has that today.

-- Randal L. Schwartz, Perl hacker

[reply]


Clear questions and runnable code get the best and fastest answer
	PerlMonks