Better dump of foreign key data

From: pgsql-bugs(at)postgresql(dot)org
To: pgsql-bugs(at)postgresql(dot)org
Subject: Better dump of foreign key data
Date: 2001-05-09 17:09:08
Message-ID: 200105091709.f49H98D28627@hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Ivn Baldo (ivan(dot)baldo(at)pilasnet(dot)com) reports a bug with a severity of 4
The lower the number the more severe it is.

Short Description
Better dump of foreign key data

Long Description
When you dump a database wich has tables that have foreign keys, it dumps a lot of things regarding foreign keys that aren't very much normal-idiot human readable.
It would be nice to have it dump things like "status integer references statuses(cod)" when dumping a table, instead of a lot of "internal-like" things.
I wonder if someday the handling of foreign keys changes, then maybe the dumped data could not be restored easily, and also its nice to have clean data about the schema of a database, etc.
This criteria should be applied to other things like simple indexes, they should be created using the "unique" keyword on the table creation (though this slows down the restore, there should be an option to pretty-dump :) ...).
All in all, this is a suggestion for more cleaner and pretty dumps.

Sample Code

No file was uploaded with this report

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Eisentraut 2001-05-09 17:55:27 Re: SELECT updatability clause defective.
Previous Message pgsql-bugs 2001-05-09 16:22:45 SELECT updatability clause defective.