Re: Imperfect solutions

> > Let me make a suggestion. Next time we have a partial fix for
> > something, but don't want to add it, let's add the item on the TODO list
> > under the heading "Imperfect Fixes," where we list items we have fixed
> > but need more work. This way, we will be able to give users a feature,
> > but we will not forget to revisit the item and make a _perfect_ fix
> > later.
>
> The first thing you should add to that list is 'Inheritance of constraints'.
> At the moment myself and Stephan are beavering away making it so that
> constraints are recusively added and removed - however if ever we make a
> pg_constraints catalog, and a one-to-many constraint->table mapping catalog,
> all our code will need to be (minimally) changed.

>
> Also, what about foreign keys? At the moment it is incredibly complicated
> to determine all the foreign keys on a table, what column(s) they're defined
> over, what column(s) they reference and what their behaviour is. And just
> try writing code (like I am) that tries to drop them by name, let alone list
> them!!!
>
> Lastly - pg_dump can happily dump foreign keys as raw triggers, but the
> perfect solution (methinks) would be to dump them as alter table add
> constraints. Makes it easier to move between different database products.

I already have on the TODO list:

* Make constraints clearer in dump file

In fact I have a whole referential integrity section of the TODO list.
Please let me know what needs to be added. Let me add:

* Make foreign keys easier to identify

--
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