From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Thom Brown <thom(at)linux(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Jim Nasby <jim(at)nasby(dot)net>, Joshua D(dot) Drake <jd(at)commandprompt(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [COMMITTERS] pgsql: Enable CHECK constraints to be declared NOT VALID |
Date: | 2011-11-24 21:50:35 |
Message-ID: | 1322171400-sup-4407@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
Excerpts from Alvaro Herrera's message of vie nov 11 00:32:33 -0300 2011:
> Excerpts from Thom Brown's message of jue nov 10 21:28:06 -0300 2011:
> >
> > On 10 November 2011 23:56, Thom Brown <thom(at)linux(dot)com> wrote:
>
> > > The dump correctly contains:
> > >
> > > CREATE TABLE a (
> > > num integer,
> > > CONSTRAINT meow CHECK ((num < 20)) NOT VALID
> > > );
> >
> > Actually I mean incorrectly contains, because the constraint needs
> > adding after the data insertion, not as part of the create table
> > statement.
>
> Interesting, thanks -- I'll look into it.
I have just pushed a fix for this. Thanks for the report and sorry for
the delay.
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Thom Brown | 2011-11-24 21:57:11 | Re: [COMMITTERS] pgsql: Enable CHECK constraints to be declared NOT VALID |
Previous Message | Alvaro Herrera | 2011-11-24 21:48:32 | pgsql: Dump an unvalidated constraint separately from its table |
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Urbański | 2011-11-24 21:56:53 | Re: PL/Python SQL error code pass-through |
Previous Message | Peter Eisentraut | 2011-11-24 20:05:09 | Re: Notes on implementing URI syntax for libpq |