![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I have a schema which includes one table with a CHECK constraint. After the schema is dumped (with pg_dump) as ascii text attempts to recreate it using the psql -f <filename> command cause this one table, called navigaion, to fail to create. This is using postgresql 7.3.3 on Redhat 9.0. The fragment of the dump is below. Is there a cure for this problem? CREATE TABLE navigation ( src_section_id integer NOT NULL, dst_section_id integer NOT NULL, rank smallint NOT NULL, CHECK ((parent_section_id <> child_section_id)) ) WITHOUT OIDS; |
#3
| |||
| |||
|
|
Further to my original message I realise that the problem was due to the text of the rule still referring to columns, src_section_id and dst_section_id by their original names, parent_section_id and child_section_id respectively. So the nature of the bug changes to that pg_dump does not correctly export CHECK rules where the name of the column(s) referred to has changed. Now IMHO that is somewhat subtle. |
![]() |
| Thread Tools | |
| Display Modes | |
| |