Tom Lane wrote:
> Chris Dunlop <[EMAIL PROTECTED]> writes:
> > One way or the other, I think either allowing the inherited
> > constraints to be dropped, or the inability of pg_dump to
> > correctly dump the resulting schema, should be considered a bug
> > rather than a lacking feature, as the curr
On Wed, Feb 22, 2006 at 10:11:51AM -0500, Tom Lane wrote:
> Chris Dunlop <[EMAIL PROTECTED]> writes:
>> E.g. using the script below, the 'bar.f1' column in the 'new'
>> database ends up with a 'not null' constraint that isn't present
>> in the 'orig' database.
>
>> create table foo (f1 integer n
Chris Dunlop <[EMAIL PROTECTED]> writes:
> One way or the other, I think either allowing the inherited
> constraints to be dropped, or the inability of pg_dump to
> correctly dump the resulting schema, should be considered a bug
> rather than a lacking feature, as the current situation results
> in
Chris Dunlop <[EMAIL PROTECTED]> writes:
> E.g. using the script below, the 'bar.f1' column in the 'new'
> database ends up with a 'not null' constraint that isn't present
> in the 'orig' database.
> create table foo (f1 integer not null);
> create table bar () inherits(foo);
> alter table b
