From: Paul Thomas <paul@tmsl.demon.co.uk>
To: Markus Bertheau <twanger@bluetwanger.de>
Cc: Dan Field <dof@llgc.org.uk>
Cc: pgsql-sql @ postgresql . org <pgsql-sql@postgresql.org>
Subject: Re: problem porting MySQL SQL to Postgres
Date: Sun, 18 Apr 2004 20:24:47 +0100
Message-ID: <20040418202447.A16735@bacon> (raw)
In-Reply-To: <1082313473.2263.0.camel@yarrow.bertheau.de>
References: <4A063822-8EC7-11D8-9677-000A958E367A@llgc.org.uk>
<20040415121523.A864@bacon>
<1082313473.2263.0.camel@yarrow.bertheau.de>
On 18/04/2004 19:37 Markus Bertheau wrote:
> В Чтв, 15.04.2004, в 13:15, Paul Thomas пишет:
> > On 15/04/2004 11:25 Dan Field wrote:
>
> > Your "= NULL" tests are also not valid SQL (should be IS NULL).
>
> I think = NULL _is_ valid SQL, it just doesn't do what you think.
It's valid in an assignment
update foo set bar = null;
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.
--
Paul Thomas
+------------------------------+---------------------------------------------+
| Thomas Micro Systems Limited | Software Solutions for
Business |
| Computer Consultants |
http://www.thomas-micro-systems-ltd.co.uk |
+------------------------------+---------------------------------------------+
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: paul@tmsl.demon.co.uk, twanger@bluetwanger.de, dof@llgc.org.uk
Subject: Re: problem porting MySQL SQL to Postgres
In-Reply-To: <20040418202447.A16735@bacon>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox