Lewis Foti wrote:
> 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
Lewis Foti wrote:
> 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 command cause this one
> table, called navigaion, to fail to create. This is using postgresql
> 7.3.3 on Redha
Hi
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
command cause this one table, called navigaion, to fail to
create. This is using postgresql 7.3.3 on Redhat 9.0. The frag
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 e
