Re: Table/Column Constraints

From: "Ross J(dot) Reedstrom" <reedstrm(at)rice(dot)edu>
To: Hannu Krosing <hannu(at)tm(dot)ee>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Table/Column Constraints
Date: 2000-11-20 17:15:53
Message-ID: 20001120111553.A26906@rice.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

Ross
--
Open source code is like a natural resource, it's the result of providing
food and sunshine to programmers, and then staying out of their way.
[...] [It] is not going away because it has utility for both the developers
and users independent of economic motivations. Jim Flynn, Sunnyvale, Calif.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Luis Magaa 2000-11-20 17:24:06 PostgreSQL as windows 2000 service
Previous Message Hannu Krosing 2000-11-20 17:06:01 Re: pl/pgsql slowness