Re: MySQL versus Postgres

On reflection, I think what is needed is a handbook that features cut
and paste code to do the things with Postgres that people do today
with MySQL.

Such a handbook, featured as the first section of the documentation,
would take readers through the steps necessary to set up an online
shopping site, for example, with Postgres. Cut and paste code is
absolutely crucial to the success of such a document.

Make it easy. Make it easy. Our road in the yellow wood has to be
the one you can go down the easiest.

John

On Aug 6, 2010, at 1:39 PM, Phillip Smith wrote:

> On 6 August 2010 16:08, Torsten Zühlsdorff <foo(at)meisterderspiele(dot)de>
> wrote:
>
> I receive my "oh wow" when i do the same things in Postgres like in
> MySQL: Writting some procedures, triggers and use foreign key. The
> "oh wow" was that it just *works*. After some years of using MySQL
> this is a very uncommon feeling, even if you are experienced which
> MySQL. ;)
>
>
> I'm going the other way -- I first started SQL/RDBMS with
> PostgreSQL, and now I'm starting to have to deal with MySQL for some
> things at work. I know exactly how to do what I want in PG, but
> doing the same thing in MySQL is ten times more complicated and has
> me pulling my hair out :(