Horton

Re: ALTER TABLE...ALTER COLUMN vs inheritance

Tom Lane <tgl@sss.pgh.pa.us>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alex Hunsaker <badalex@gmail.com>
Cc: Bernd Helmle <mailings@oopsware.de>, pgsql-hackers@postgresql.org
Date: 2009-11-16T18:45:38Z
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. Catalog NOT NULL constraints

Alex Hunsaker <badalex@gmail.com> writes:
> FYI defaults have the same problem.   Would it be awkward would it be
> to use pg_constraint for the book keeping as well? [ and by that I
> really mean ALTER TABLE ADD CONSTRAINT my_default DEFAULT .... so you
> can give them a name ]

That sounds moderately insane to me.  Why would you need a name?
What would it mean to have more than one default attached to a column?

			regards, tom lane