Hello Peter,
a bit late, but just ran into the same problem while testing an upgrade.
Rather than uncommenting the lines you should drop the constraints with:
ALTER TABLE community2collection DROP CONSTRAINT $2;
ALTER TABLE collection2item DROP CONSTRAINT $2;
ALTER TABLE community2community
I wanted to see if anyone else has run into the issue when upgrading to 1.6
(rc1) from 1.5.2, that
ERROR: constraint community2collection_collection_id_fkey of relation
community2collection does not exist
ERROR: constraint community2community_child_comm_id_fkey of relation
community2community
Hi Peter,
this sql is intended to fix the name of some constraint that we need to
make deferrable.
The drop sentence is make with the assumption that postgres has
created the foreign key with a standard syntax, this is which that I
have seen on many postgres instances that I run on my workstation
3 matches
Mail list logo
