Horton

Re: creating CHECK constraints as NOT VALID

Alvaro Herrera <alvherre@commandprompt.com>

View thread
From: Alvaro Herrera <alvherre@commandprompt.com>
To: Jaime Casanova <jaime@2ndquadrant.com>
Cc: Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2011-05-31T16:48:02Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Fix pg_get_constraintdef to cope with NOT VALID constraints

Excerpts from Alvaro Herrera's message of mar may 31 12:39:48 -0400 2011:
> Excerpts from Jaime Casanova's message of mar may 31 12:24:09 -0400 2011:
> > On Tue, May 31, 2011 at 11:04 AM, Alvaro Herrera
> > <alvherre@alvh.no-ip.org> wrote:
> > > This patch allows you to initially declare a CHECK constraint as NOT
> > > VALID
> > 
> > seems you forgot to add the patch itself
> 
> oops ... another bug in my email client, it seems.

Hmm, found an inconsistency in the way recursion is handled -- other
commands have a AT_DoFooRecurse case.  Weird.  I'll change this to be
like that, though I don't readily see why we do it that way.

-- 
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support