| From: | Manfred Koizar <mkoi-pg(at)aon(dot)at> |
|---|---|
| To: | shridhar_daithankar(at)persistent(dot)co(dot)in |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Updates with NULL |
| Date: | 2003-09-15 15:20:16 |
| Message-ID: | d9lbmv0e1t2heru25jhrk5vljjafrkp79t@email.aon.at |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, 15 Sep 2003 19:34:48 +0530, "Shridhar Daithankar"
<shridhar_daithankar(at)persistent(dot)co(dot)in> wrote:
>Update foo set somefield=NULL where somefield >9;
>
>Now I am not sure having something equalled with NULL is a good thig logically.
It doesn't matter whether I agree. The standard does not. SQL92 says
<set clause> ::=
<object column> <equals operator> <update source>
<equals operator> ::= =
<update source> ::=
<value expression>
| <null specification>
| DEFAULT
<null specification> ::=
NULL
SQL99 is much more verbose and difficult to read, but it is very clear
that the assignment operator in a set clause has to be "=".
Servus
Manfred
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jason Tishler | 2003-09-15 15:22:47 | Re: The NT services Cygwin PostgreSQL installatio |
| Previous Message | Tom Lane | 2003-09-15 15:17:58 | Re: Updates with NULL |