Re: MySQL vs postgres

[awilliam@xxxxxxxxxxxxx]

>You can see a comparison among some SQL servers such as MySQL, 
PostgreSQL,
>M$SQL 7, Sybase, Oracle 8
>... at www.postgresql.org. At first, I like MySQL much because many 
people use
>it and there are many
>applications using it. Now I see that it doesn't support something 
(e.g nested
>subqueries), while postgresql does. Now I don't know what I should 
choose.
>Does anybody give me a suggestion?

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.  But if you are simply using the 
Database to store information used to generate pages (etc...) then I 
think "simulations" of nested queries is adequate.  My real suggestion 
is to write any app to use ODBC and not a specific DB so you can 
choose whatever is appropriate in the future (your project gets really 
big and you need something like Oracle) and not have to worry about 
how happy/unhappy your applications will be with your decision.

>>Does anyone know the main difference between these two SQL 
implementations?
>>(MySQL and Postgres) Because I've been studiing MySQL for about 
about three
>>weeks now ... and I've come across a SQL construct that MySQL does 
not
>>support ..... which is views ....... I know nothing about postgress 
but I'm
>>wondering is postgres more SQL-92 compliant than MySQL? I really 
like MySQL
>>but I want to stay with the most compliant SQL implementation (at 
least
>>while I'm in process of learning SQL). Thank you.