Re: MySQL vs postgres

["imago" <imago@xxxxxxxxxxx>]

> There are programmatic ways to "simultae" nested subqueries.  But
if
> you need them on a pretty regular basis it might be easier to use
a DB
> that supports them.    It also depends on if you are updating your
> database based on those queries, and whether multiple updates may
> occur at the "same" time.  If both are true then I think you need
> transactions (in order to make the action atomic) and record
locking,
> which are not supported by MySQL

My application would benifit by record locking so I am thinking
postgres is the right tool to use.

As a novice user of linux, SQL type db's apache and php, I have
noticed that the books I have aimed at getting the php web system
environment compiled, installed and running say little or nothing
about postgres. They giveexplicit commands and directions to use
MySql!

Why is this? Heavy traffic on web applications, like a real time
auction, hopefilly will have many concurrent users and overlapping
sessions working on the same records in the same tables.  Seems to
me record locking is essential for accuracy and efficienncy.

Are there other issues why MySQL is the db of choice for people who
write the php books?

imago