It appears that some of these errors are due to the parent table being
populated after the child table. Can I control the order of the copy
statements in my script when I run the pg_dump?
Stephan Szabo wrote:
On Fri, 10 Oct 2003, Jodi Kanter wrote:
Ok. sorry to confuse everyone...I got my restore to fun to completion so
apparently my question about running restores in psql and the ordering
of the data are not relevant.
I do, however, have one other question I'd like to pose.
I am getting serveral ref integrity errors which state that a FK value
in one table does not exist in its parent table. However, when I go to
the database to confirm this I can find no data that violates the
constraint. Could the error be pointing to something less obvious?
Hmm, two possibilities I can think off the top of my head are if the fk
values are being inserted and erroring and the pk rows are being done
after (which would make a later check look like this) or if there's any
inheritance involved (where a plain select will show child rows that don't
currently participate in the foreign key constraint).
--
________________________________
_______________________________
Jodi L Kanter
BioInformatics Database Administrator
University of Virginia
(434) 924-2846
[EMAIL PROTECTED]
|
