Deleting a primary bitstream does not clear the primary_bitstream_id on the
bundle table
----------------------------------------------------------------------------------------
Key: DS-197
URL: http://jira.dspace.org/jira/browse/DS-197
Project: DSpace 1.x
Issue Type: Bug
Affects Versions: 1.5.2, 1.5.1, 1.5.0
Reporter: Graham Triggs
If you delete a bitstream that is marked as a 'primary' bitstream, then the
primary_bitstream_id field on the bundle table is not cleared.
As this is a foreign key relationship, it causes an integrity constraint
violation when the cleanup script attempts to remove the bitstream.
Further, as the cleanup script doesn't isolate each bitstream cleanup, it has
the effect of stopping the cleanup script from clearing any deleted bitstreams
in that repository.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.dspace.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Register Now & Save for Velocity, the Web Performance & Operations
Conference from O'Reilly Media. Velocity features a full day of
expert-led, hands-on workshops and two days of sessions from industry
leaders in dedicated Performance & Operations tracks. Use code vel09scf
and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
