What about transactions ? In all the discussion noone points that
PostgreSQL uses them. Maybe noone uses transactions so they have no
matter.
--
Krzysztof Dziekiewicz
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
> Not to cause a flame war, but, MySQL and PostgreSQL are both excellent
> choices, MySQL tends to be a lighter less feature rich database while
> PostgreSQL tends to have more features, perform better under load, etc.
Under differing types of load, yes. MySQL is more hit-based, while
PostgreSQL d
Not to cause a flame war, but, MySQL and PostgreSQL are both excellent
choices, MySQL tends to be a lighter less feature rich database while
PostgreSQL tends to have more features, perform better under load, etc.
You can read a lot about the two databases at google.com and also at
postgresql.org.
> See MySQL 4.x. They also have subselects now (HUGE!). As for an
Well, not really. Nested queries are scheduled for 4.1. 4.0 is in
gamma, 4.1 isn't even available for download as alpha. You'll have to go
with Postgres for now if you need subselects.
Regarding row locking and transactions, lo
> > I'm just deciding which DB to use for my projects and I'm not clear with
one
> > thing... When considering a database for web, is MySQL good enough? I
read
> > it only supports table locking, which is not very satisfying in such a
> > multiuser environment as the internet..
>
> PostgreSQL has t
>> is MySQL good enough? I read it only supports table locking,
>> which is not very satisfying in such a multiuser environment
>> as the internet..
Read all of http://www.mysql.com/doc/en/ANSI_diff_Transactions.html
You'll find an explanation of what atomic operations are and how they
compare to
> I'm just deciding which DB to use for my projects and I'm not clear with one
> thing... When considering a database for web, is MySQL good enough? I read
> it only supports table locking, which is not very satisfying in such a
> multiuser environment as the internet..
PostgreSQL has transactions
Both databases work well for what they are intended to do.
Either database will have good basic performance, however PostgreSQL has
had more advanced features and stability in the past some of which MySQL
has worked on gaining.
Last I heard there was still issues with complex operations and tab
Youy are unlikely to egt balanced asvice on this in the MySQL or
Postgress lists -after all those people have already made thier decision.
I haven't used Postgress much - but basically...
Mysql - available on loads of hosting packages, very large user base.
PostgreSQL - better adherance to ANS
Miro, et al --
...and then Miro Kralovic said...
%
% Hi,
Hello!
%
% I'm just deciding which DB to use for my projects and I'm not clear with one
% thing... When considering a database for web, is MySQL good enough? I read
% it only supports table locking, which is not very satisfying in such
You accidentally published this to the wrong email list. I assume you meant to send
this
to the MySQL email list.
- Original Message -
From: "Miro Kralovic" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, December 23, 2002 9:10 AM
Subject: [PHP] MySQL vs PostgreSQL
> Hi,
>
>
http://www.phpbuilder.com/columns/tim20001112.php3?page=1
-jack
-Original Message-
From: Brent Langston [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 08, 2001 1:22 PM
To: PHP General List
Subject: [PHP] MySql vs PostgreSQL
So, I've noticed that most of you talk about PHP/MySQL almost e
12 matches
Mail list logo
