SQL compatibility reminder: MySQL vs PostgreSQL
in [PgSql]
|
Prev: Visual Studio 2005, C-language function - avoiding hacks?
Next: [HACKERS] Core dump running PL/Perl installcheck with bleadperl [PATCH]
From: "Joshua D. Drake" on 5 Mar 2010 15:17 On Fri, 2010-03-05 at 15:10 -0500, Andrew Dunstan wrote: > > David Fetter wrote: > > On Fri, Mar 05, 2010 at 02:56:23PM +0100, François Pérou wrote: > > > >> Dear friends, > >> > >> As a reminder, I took part in the development of pgAdmin and I am > >> not looking for a flame war. > >> > > > > You're doing a poor job on that latter. You asked before for the > > PostgreSQL project to "address" the concerns of some, but by no means > > all, developers of some little project by introducing massive bugs. > > > > Drupal is not a little project. Let's keep our own facts straight. Not it isn't, it dwarfs us I am sure. It is within our interest to work with them but in a proper way. As I have said, Drupal 7 addresses most of our concerns, so anything we want to complain about should be in the interest of making sure Drupal 7 works properly, not previous versions. Sincerely, Joshua D. Drake > > cheers > > andrew > > -- PostgreSQL.org Major Contributor Command Prompt, Inc: http://www.commandprompt.com/ - 503.667.4564 Consulting, Training, Support, Custom Development, Engineering Respect is earned, not gained through arbitrary and repetitive use or Mr. or Sir. -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: David Fetter on 5 Mar 2010 15:21 On Fri, Mar 05, 2010 at 03:10:59PM -0500, Andrew Dunstan wrote: > > > David Fetter wrote: > >On Fri, Mar 05, 2010 at 02:56:23PM +0100, Fran�ois P�rou wrote: > >>Dear friends, > >> > >>As a reminder, I took part in the development of pgAdmin and I am > >>not looking for a flame war. > > > >You're doing a poor job on that latter. You asked before for the > >PostgreSQL project to "address" the concerns of some, but by no means > >all, developers of some little project by introducing massive bugs. > > Drupal is not a little project. Let's keep our own facts straight. Drupal 6 support is, given its finite future. He's basically asking us to do something that Drupal 7 and later won't need or want, so I stick by "little." Cheers, David. -- David Fetter <david(a)fetter.org> http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: david.fetter(a)gmail.com iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Dave Page on 5 Mar 2010 15:30 On Fri, Mar 5, 2010 at 6:25 PM, Robert Haas <robertmhaas(a)gmail.com> wrote: > On Fri, Mar 5, 2010 at 9:55 AM, Dave Page <dpage(a)pgadmin.org> wrote: >> 2010/3/5 François Pérou <francois.perou(a)free.fr>: >>> Dear friends, >>> >>> As a reminder, I took part in the development of pgAdmin and I am not >>> looking for a flame war. >> >> What did you work on François? I can't find your name in my email >> archives or on archives.postgresql.org. > > I believe the OP is the same person as Jean-Michel Poure Yeah, I had email from him offlist. FYI, whilst I disagree that we should break Postgres for the sake of some lazy developers on another project, Jean-Michel was a long-term major contributor to pgAdmin I and II and I have a lot of respect for him and am extremely grateful for his past work on the project. -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com PG East Conference: http://www.enterprisedb.com/community/nav-pg-east-2010.do -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Robert Haas on 5 Mar 2010 15:40 On Fri, Mar 5, 2010 at 3:30 PM, Dave Page <dpage(a)pgadmin.org> wrote: > On Fri, Mar 5, 2010 at 6:25 PM, Robert Haas <robertmhaas(a)gmail.com> wrote: >> On Fri, Mar 5, 2010 at 9:55 AM, Dave Page <dpage(a)pgadmin.org> wrote: >>> 2010/3/5 François Pérou <francois.perou(a)free.fr>: >>>> Dear friends, >>>> >>>> As a reminder, I took part in the development of pgAdmin and I am not >>>> looking for a flame war. >>> >>> What did you work on François? I can't find your name in my email >>> archives or on archives.postgresql.org. >> >> I believe the OP is the same person as Jean-Michel Poure > > Yeah, I had email from him offlist. FYI, whilst I disagree that we > should break Postgres for the sake of some lazy developers on another > project, Jean-Michel was a long-term major contributor to pgAdmin I > and II and I have a lot of respect for him and am extremely grateful > for his past work on the project. That is good to hear. I do not think (nor do I think anyone else here thinks) that making Drupal work with PostgreSQL is a bad idea, and I hope that he and others will continue to pursue that goal - 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. ....Robert -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Chris Browne on 5 Mar 2010 16:14
francois.perou(a)free.fr (Fran�ois P�rou) writes: > * I am very surprised by the SQL level of Php developers. The example > Drupal developers trying to rewrite SQL queries dynamically adding > DISTINCT clause is just an example. So don't expect them to understand > the difference between MySQL and PostgreSQL. It is out of reach. They > focuse on Php code. If they refuse to contemplate suggestions as to how to write more portable SQL queries that would work with databases other than MySQL, then I don't know what constructive discussion there can be about this. > I believe that PostgreSQL should support more MySQLisms in order to BEAT > MySQL. Why, when the MySQLisms in questions are divergences from the SQL standards, and the issue seems to bite all the other databases in more or less the same way? It doesn't seem to me that the answer to "Drupal developers refuse to consider writing portable SQL" is to try to impose MySQL's divergences from SQL onto all the *other* DBMSes. -- "Have you noticed that, when we were young, we were told that `everybody else is doing it' was a really stupid reason to do something, but now it's the standard reason for picking a particular software package?" -- Barry Gehm |