Re: problem porting MySQL SQL to Postgres

From: Bruno Wolff III <bruno(at)wolff(dot)to>
To: Paul Thomas <paul(at)tmsl(dot)demon(dot)co(dot)uk>
Cc: Markus Bertheau <twanger(at)bluetwanger(dot)de>, Dan Field <dof(at)llgc(dot)org(dot)uk>, "pgsql-sql (at) postgresql (dot) org" <pgsql-sql(at)postgresql(dot)org>
Subject: Re: problem porting MySQL SQL to Postgres
Date: 2004-04-19 03:21:57
Message-ID: 20040419032157.GB1881@wolff.to
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

On Sun, Apr 18, 2004 at 20:24:47 +0100,
Paul Thomas <paul(at)tmsl(dot)demon(dot)co(dot)uk> wrote:
>
> PostgreSQL can be coerced into accepting where foo = null with the
> transform_null_equals run-time option but that doesn't make it legal SQL
> IFAIK.

foo = NULL is a valid SQL expression that always returns NULL.

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message Gary Stainburn 2004-04-19 12:47:28 three-way join
Previous Message Paul Thomas 2004-04-18 19:24:47 Re: problem porting MySQL SQL to Postgres