On Tue, 2010-08-31 at 20:17 -0400, Merlin Moncure wrote: > > This is where the interesting thing happens: On MySQL the query actually > > works as intended, but it doesn't on PostgreSQL. As I said, I'm sure this is > > not a bug in PostgreSQL, but the lack of a stupid user trick. While my > > project is on MySQL, and I could theoretically leave my code as is to take > > advantage of this trick, I'm sure I'd be a complete idiot to leave it > > instead of fixing it. > > You have it backwards, mysql is broken, postgresql is not. That is what he said. JD -- PostgreSQL.org Major Contributor Command Prompt, Inc: http://www.commandprompt.com/ - 509.416.6579 Consulting, Training, Support, Custom Development, Engineering http://twitter.com/cmdpromptinc | http://identi.ca/commandprompt -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
