Re: [HACKERS] SQL compatibility reminder: MySQL vs PostgreSQL

2010-03-06 Thread François Pérou
Le samedi 06 mars 2010 à 11:01 -0800, Josh Berkus a écrit : However, The server is free to return any value from the group doesn't sound like the way we do things, ever. MySQL users might be OK with queries which return an indeterminate answer; our users are not. You'll notice that SELECT

[HACKERS] SQL compatibility reminder: MySQL vs PostgreSQL

2010-03-05 Thread François Pérou
Dear friends, As a reminder, I took part in the development of pgAdmin and I am not looking for a flame war. I would like to point out Drupal community efforts (including myself) to write down the most frequent problems when porting MySQL from/to PostgreSQL: The main MySQL/PostgreSQL issues can

Re: [HACKERS] SQL compatibility reminder: MySQL vs PostgreSQL

2010-03-05 Thread François Pérou
Thanks for your answers. To speak frankly: * I wrote the Drupal guide for porting from MySQL to PostgreSQL. * I am also the author of remarks about people should use PostgreSQL to write portable SQL. * I am very surprised by the SQL level of Php developers. The example Drupal developers

Re: [HACKERS] SQL compatibility reminder: MySQL vs PostgreSQL

2010-03-05 Thread François Pérou
Le vendredi 05 mars 2010 à 15:40 -0500, Robert Haas a écrit : having said that, asking us to make changes that are not based on solid technical arguments, don't conform to the SQL standard, and most important that we already clearly said we were not going to make is not the way to get there.