pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Scott Marlowe <scott.marlowe@gmail.com>
To: Andy Shellam <andy-lists@networkmail.eu>
Cc: pgsql-sql@postgresql.org
Subject: Re: CHECK constraint removing brackets
Date: Mon, 11 Jan 2010 13:14:12 -0700
Message-ID: <dcc563d11001111214p3cd20de4rf65d8d591b3e4cca@mail.gmail.com> (raw)
In-Reply-To: <D884BF27-7555-40BA-8A5E-CAEE1272CE26@networkmail.eu>
References: <D884BF27-7555-40BA-8A5E-CAEE1272CE26@networkmail.eu>

On Mon, Jan 11, 2010 at 12:49 PM, Andy Shellam
<andy-lists@networkmail.eu> wrote:
> With the above in mind, I decided on the following check to enforce this:
>
> (state = 'Unconfirmed'::client.order_state AND invoice_id = NULL) OR (state != 'Unconfirmed'::client.order_state AND invoice_id != NULL)

Nothing can = null.  and invoice_id IS NULL is the proper
nomenclature.  Also, something <> NULL makes no sense, because we
don't know what NULL is, so that becomes something IS NOT NULL

Also != is not proper SQL, although many dbs understand it, <> is the
proper way to write NOT EQUAL TO.

> However PostgreSQL (8.4.2) converts this to the following:
>
> state = 'Unconfirmed'::client.order_state AND invoice_id = NULL::integer OR state <> 'Unconfirmed'::client.order_state AND invoice_id <> NULL::integer

ANDs have priority of ORs so the removal of the parenthesis makes no
great change here.  also, SQL standard is <> not !=.

I'm guessing the real problems here are your NULL handling.  See if
changing it to IS NULL / IS NOT NULL gets you what you want.



view thread (5+ messages)  latest in thread

Message-ID: <dcc563d11001111214p3cd20de4rf65d8d591b3e4cca@mail.gmail.com>
Permalink:  ../dcc563d11001111214p3cd20de4rf65d8d591b3e4cca@mail.gmail.com/
Also on:    postgresql.org/message-id/dcc563d11001111214p3cd20de4rf65d8d591b3e4cca@mail.gmail.com

 · 

reply

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: scott.marlowe@gmail.com, andy-lists@networkmail.eu
  Subject: Re: CHECK constraint removing brackets
  In-Reply-To: <dcc563d11001111214p3cd20de4rf65d8d591b3e4cca@mail.gmail.com>

* 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