Re: BUG #5053: domain constraints still leak

From: Sam Mason <sam(at)samason(dot)me(dot)uk>
To: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5053: domain constraints still leak
Date: 2009-09-14 15:58:50
Message-ID: 20090914155850.GY5407@samason.me.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On Mon, Sep 14, 2009 at 10:54:07AM -0500, Kevin Grittner wrote:
> Sam Mason <sam(at)samason(dot)me(dot)uk> wrote:
> > the deeper problem seems to be that the table was created as:
> >
> > create table test (a tstdom);
> >
> > and not as:
> >
> > create table test (a tstdom not null);
>
> Given that tstdom is declared as NOT NULL, is this difference
> considered a *feature* or is it an implementation quirk?

That's why I pointed it out!

Based on my reading of the SQL spec (and reading about Codd's
descriptions of domains) I'd say it was a bug/implementation quirk.

--
Sam http://samason.me.uk/

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2009-09-14 16:28:24 Re: ERROR: invalid page header in block 502758 of relation base/16388/16403
Previous Message Kevin Grittner 2009-09-14 15:54:07 Re: BUG #5053: domain constraints still leak

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2009-09-14 16:05:24 Re: Streaming Replication patch for CommitFest 2009-09
Previous Message Pavel Stehule 2009-09-14 15:56:56 Re: [PATCH] 8.5 plpgsql change for named notation: treat word following AS keyword as label v3