Re: ADD/DROPS inherits

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Greg Stark <gsstark(at)mit(dot)edu>
Cc: pgsql-patches(at)postgresql(dot)org
Subject: Re: ADD/DROPS inherits
Date: 2006-06-13 21:32:39
Message-ID: 1150234360.13699.93.camel@localhost.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

On Mon, 2006-06-12 at 17:39 -0400, Greg Stark wrote:

> Points I'm uncertain about:
>
> . I throw an elog() error if there's a null conbin for a CHECK constraint. Is
> it possible for a valid CHECK constraint structure to have a null conbin?

ruleutils shows: elog(ERROR, "null conbin for constraint %u"

> I added some basic (very basic) regression tests

Should we fail if columns in the wrong order from the parent? I thought
that was one of the restrictions you discovered?

Can we test for
ALTER TABLE child NO INHERIT parent1 INHERIT parent2
That was on Hannu's wish list.

Is INHERIT allowed or disallowed with other ALTER TABLE options?
If it is allowed, can we test for something that will fail and something
that would pass, e.g. ALTER TABLE DROP column1 INHERITS parent -- where
the parent passes on column1.

When I read those tests, it makes me think this should be INHERITS and
NOT INHERITS (not great English, but then neither is NO INHERIT).
ISTM it might become confusing between INHERITS and INHERIT.
Waddyathink?

--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Greg Stark 2006-06-13 22:48:40 ADD/DROPS INHERIT (actually INHERIT / NO INHERIT)
Previous Message Simon Riggs 2006-06-13 15:19:39 Re: [PATCHES] Non-transactional pg_class, try 2