Hi Claudia,
I ran pg_dump, as you suggested (see attached), and it looks like all the
three tables (collection2item, community2community, and
community2collection) have 1 foreign key only each. For instance, the
error that I receive complains about comm2coll table not having the
collection_fk
Hello Stanislav,
you most likely did not run into the problem, because you never tried to delete
anything. There might be issues with collection2item, community2community, too
if my guess is right that this was this old issue:
http://dspace.2283337.n4.nabble.com/Dspace-tech-running-the-15-to-16
Thank you Claudia,
We started ten years ago and went through a few upgrades. I can see how
this problem might have been created during the process, but we never ran
into the problem until now. If I look at foreign keys for
community2collection table, I see this:
Name: community2collection_co
Hello Stanislav,
are you using Postgres or Oracle and is this an original 4.0
installation or did you upgrade from an older version?
If you are using Postgres and did upgrade there may have been an issue
with the upgrade process.
The constraint is here:
https://github.com/DSpace/DSpace/blob/dspac
Greetings!
When I try to delete collections in DSpace 4.0 on Windows Server 2008, I
have the following error:
org.postgresql.util.PSQLException: ERROR: constraint
"comm2coll_collection_fk" does not exist
Our PostgreSQL has a "community2collection" table with one foreign key -
"community_id" -
Greetings!
When I try to delete collections in DSpace 4.0 on Windows Server 2008, I
have the following error:
org.postgresql.util.PSQLException: ERROR: constraint
"comm2coll_collection_fk" does not exist
Our PostgreSQL has a "community2collection" table with one foreign key -
"community_id" -
