Re: Table/Column Constraints

> "Ross J. Reedstrom" <reedstrm(at)rice(dot)edu> writes:
> > On Mon, Nov 20, 2000 at 06:52:20PM +0200, Hannu Krosing wrote:
> >>
> >> Dumping constraints in human-readable form (instead of CREATE CONSTRAIN
> >> TRIGGER) would also be great.
>
> > In fact, IMHO, this would be a great place to start: we'd all love the
> > fuctionality, it'd have you examining almost all the same code, and it'd
> > be a feature we could all test, in diverse situations. DROP CONSTRAINT
> > is unlikely to be as widely tested. If you can build the introspection
> > correctly, so that it dumps/reloads correctly for _everyone_, then I'd
> > trust your DROP CONSTRAINT work a lot more.
>
> Yes. My take on this is that a lot of the constraint-related stuff,
> especially foreign keys, is misdesigned: the reason it's so hard to
> extract the info is that we are only storing an execution-oriented
> representation. There should be a purely declarative representation
> of each constraint someplace, too, for ease of introspection.

Yes, and psql should be able to show constraint info too.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026