Re: ALTER TABLE...ALTER COLUMN vs inheritance

Bernd Helmle <mailings@oopsware.de>

From: Bernd Helmle <mailings@oopsware.de>

To: Bernd Helmle <mailings@oopsware.de>, Selena Deckelmann <selenamarie@gmail.com>

Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>

Date: 2010-09-14T22:41:19Z

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 →

Catalog NOT NULL constraints
- e056c557aef4 16.0 landed

Attachments

notnull_constraint.patch (application/octet-stream) patch

--On 23. Juli 2010 09:23:56 +0200 Bernd Helmle <mailings@oopsware.de> wrote:

> I'm going to delay this patch until the next commitfest. I'm able to work
> on it only sporadically during the next two weeks, and some remaining
> issues need my attention on this patch:
>
> - ALTER TABLE SET NOT NULL works not properly
> - ALTER TABLE child NO INHERIT parent leaves inconistent state in
> pg_constraint
> - Special case in pg_get_constraintdef_worker() needs more thinking

Attached is my current progress on this work. It handles ALTER TABLE ... 
[NO] INHERIT and NOT NULL constraints the same way we do with CHECK 
constraints now. ALTER TABLE SET NOT NULL still lags support for this (ran 
out of time to this commitfest deadline), but if nobody complains i would 
like to add this to the current commitfest as WIP to hear other opinions 
about the current approach again.

-- 
Thanks

	Bernd