Skip site navigation (1) Skip section navigation (2)

Re: how to create a non-inherited CHECK constraint in CREATE TABLE

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: how to create a non-inherited CHECK constraint in CREATE TABLE
Date: 2012-01-17 17:07:41
Message-ID: 1326819996-sup-6152@alvh.no-ip.org (view raw or flat)
Thread:
Lists: pgsql-hackers
Excerpts from Peter Eisentraut's message of mar ene 17 13:59:57 -0300 2012:
> It appears that the only way to create a non-inherited CHECK constraint
> is using ALTER TABLE.  Is there no support in CREATE TABLE planned?
> That looks a bit odd.

There are no plans to do that AFAIR, though maybe you could convince
Nikhil to write the patch to do so.

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

In response to

Responses

pgsql-hackers by date

Next:From: Matteo BeccatiDate: 2012-01-17 17:10:11
Subject: Re: automating CF submissions (was xlog location arithmetic)
Previous:From: Peter EisentrautDate: 2012-01-17 17:06:04
Subject: Re: Should I implement DROP INDEX CONCURRENTLY?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group