X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org
Received: from localhost (unknown [200.46.204.2])
	by svr1.postgresql.org (Postfix) with ESMTP id 7C034D1E98C
	for <pgsql-sql-postgresql.org@localhost.postgresql.org>;
	Mon, 19 Apr 2004 00:18:10 -0300 (ADT)
Received: from svr1.postgresql.org ([200.46.204.71])
	by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024)
	with ESMTP id 26870-01
	for <pgsql-sql-postgresql.org@localhost.postgresql.org>;
	Mon, 19 Apr 2004 00:18:04 -0300 (ADT)
Received: from wolff.to (wolff.to [66.93.249.74])
	by svr1.postgresql.org (Postfix) with SMTP id 4D448D1B49B
	for <pgsql-sql@postgresql.org>; Mon, 19 Apr 2004 00:18:03 -0300 (ADT)
Received: (qmail 1968 invoked by uid 500); 19 Apr 2004 03:21:57 -0000
Date: Sun, 18 Apr 2004 22:21:57 -0500
From: Bruno Wolff III <bruno@wolff.to>
To: Paul Thomas <paul@tmsl.demon.co.uk>
Cc: Markus Bertheau <twanger@bluetwanger.de>, Dan Field <dof@llgc.org.uk>,
	"pgsql-sql @ postgresql . org" <pgsql-sql@postgresql.org>
Subject: Re: problem porting MySQL SQL to Postgres
Message-ID: <20040419032157.GB1881@wolff.to>
Mail-Followup-To: Paul Thomas <paul@tmsl.demon.co.uk>,
	Markus Bertheau <twanger@bluetwanger.de>,
	Dan Field <dof@llgc.org.uk>,
	"pgsql-sql @ postgresql . org" <pgsql-sql@postgresql.org>
References: <4A063822-8EC7-11D8-9677-000A958E367A@llgc.org.uk>
	<20040415121523.A864@bacon>
	<1082313473.2263.0.camel@yarrow.bertheau.de>
	<20040418202447.A16735@bacon>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040418202447.A16735@bacon>
User-Agent: Mutt/1.5.6i
X-Virus-Scanned: by amavisd-new at postgresql.org
X-Archive-Number: 200404/157
X-Sequence-Number: 17532

On Sun, Apr 18, 2004 at 20:24:47 +0100,
  Paul Thomas <paul@tmsl.demon.co.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.