pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Joshua D. Drake <jd@commandprompt.com>
To: Rodrigo De Leon <rdeleonp@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: 8.1 Unique Index Issue/Bug???
Date: Thu, 13 Jul 2006 11:44:42 -0700
Message-ID: <44B6949A.7070209@commandprompt.com> (raw)
In-Reply-To: <a55915760607130932w47277ce0p397b6af896bfc36c@mail.gmail.com>
References: <1d219a6f0607130740g7fe13967t48c77a64fde977aa@mail.gmail.com>
	<a55915760607130932w47277ce0p397b6af896bfc36c@mail.gmail.com>


>> Why is PostgreSQL not enforcing this index? This appears to be a pretty
>> major a bug?  It would seem that you could have a unique index across
>> columns that might have a null in them.
> 
> From:
> 
> http://www.postgresql.org/docs/8.1/interactive/indexes-unique.html
> 
> Quote:
> 
> "When an index is declared unique, multiple table rows with equal
> indexed values will not be allowed. Null values are not considered
> equal. A multicolumn unique index will only reject cases where all of
> the indexed columns are equal in two rows."

To further this... in PostgreSQL:

IS NULL != ''

'' is a blank string and thus an actual value where IS NULL is nothing, 
vapor, a blackhole.

That is why IS NULL can be placed in a unique index because it isn't 
actually there (in the theorectical sense).

Sincerely,

Joshua D. Drake



> 
> Regards,
> 
> Rodrigo
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
> 


-- 

    === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
    Providing the most comprehensive  PostgreSQL solutions since 1997
              http://www.commandprompt.com/





view thread (10+ messages)  latest in thread

Message-ID: <44B6949A.7070209@commandprompt.com>
Permalink:  ../44B6949A.7070209@commandprompt.com/
Also on:    postgresql.org/message-id/44B6949A.7070209@commandprompt.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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: jd@commandprompt.com, rdeleonp@gmail.com
  Subject: Re: 8.1 Unique Index Issue/Bug???
  In-Reply-To: <44B6949A.7070209@commandprompt.com>
  References: <1d219a6f0607130740g7fe13967t48c77a64fde977aa@mail.gmail.com> <a55915760607130932w47277ce0p397b6af896bfc36c@mail.gmail.com> <44B6949A.7070209@commandprompt.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