Filippos, When you upgraded to 1.4.x, the DCVALUE table should have been deleted after it's contents were migrated over to METADATAVALUE, and a view put in it's place.
It looks like this hasn't happened, and that you still have a DCVALUE table in your database, that has it's old contents (and there is no code in 1.4.x to maintain). Check that you correctly have a METADATAVALUE table (with the correct contents), and then you should be able to safely delete the DCVALUE table (and replace it with a view - although that probably won't be necessary). Take a look at etc/database_schema_13-14.sql for more information. G On Wed, 2008-01-09 at 15:47 +0200, Filippos Kolovos wrote: > Dear all, > > Recently I am dealing with a problem with my Dspace installation > (1.4.2). > When I try to delete a collection and/or community from Dspace > the system returns an "Internal Server Error". The explanation > of this error is shown below: > > Exception: > org.postgresql.util.PSQLException: ERROR: update or delete on "item" > violates foreign key constraint "$1" on "dcvalue" > > at > org.postgresql.util.PSQLException.parseServerError(PSQLException.java:139) > at org.postgresql.core.QueryExecutor.executeV3(QueryExecutor.java:152) > at org.postgresql.core.QueryExecutor.execute(QueryExecutor.java:100) > at org.postgresql.core.QueryExecutor.execute(QueryExecutor.java:43) > at > org.postgresql.jdbc1.AbstractJdbc1Statement.execute(AbstractJdbc1Statement.java:517) > at > org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:50) > at > org.postgresql.jdbc1.AbstractJdbc1Statement.executeUpdate(AbstractJdbc1Statement.java:273) > at > org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:101) > at > org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:101) > at > org.dspace.storage.rdbms.DatabaseManager.updateQuery(DatabaseManager.java:519) > etc, etc > .......... > ......... > > The exact reason for this error seems to be that the collection id is > referenced from another table, but isn't that what the > system is supposed to do when deleting a community/collection? > Shouldn't all the relations be deleted and/or get handled by > the Dspace system? > > If I go manually into the Postgres and delete all the "relations" of > one collection by hand then the items related to that collection > remain > in the tables. I then have to do the "manual deletion" process by hand > for each item, something which is not very efficient when dealing > with thousands of records (items). > > Does anyone have had this problem before? > > Kind Regards, > > -Fk > > -- > Filippos Kolovos > Software Systems Analyst & Engineer > M.Sc. (Eng.) in Data Communications > > Automation & Networking Department > University of Macedonia Library > Egnatia 156, P.O.Box 1591 > 540 06 Thessaloniki, Greece > > E-Mail: [EMAIL PROTECTED], > [EMAIL PROTECTED] > Profile: http://www.linkedin.com/in/filipposkolovos > ----------------------------------------------------------------------- > > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace > _______________________________________________ DSpace-tech mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/dspace-tech This email has been scanned by Postini. For more information please visit http://www.postini.com ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
