Skip site navigation (1) Skip section navigation (2)

Re: problem porting MySQL SQL to Postgres

From: Paul Thomas <paul(at)tmsl(dot)demon(dot)co(dot)uk>
To: Markus Bertheau <twanger(at)bluetwanger(dot)de>
Cc: 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-18 19:24:47
Message-ID: 20040418202447.A16735@bacon (view raw or flat)
Thread:
Lists: pgsql-sql
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   |
+------------------------------+---------------------------------------------+

In response to

Responses

pgsql-sql by date

Next:From: Bruno Wolff IIIDate: 2004-04-19 03:21:57
Subject: Re: problem porting MySQL SQL to Postgres
Previous:From: Markus BertheauDate: 2004-04-18 18:37:53
Subject: Re: problem porting MySQL SQL to Postgres

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group