Thanks. Recovered from backup.
-------------------------------------------------------------
John Furfey
Digital Systems and Services Coordinator
MBLWHOI Library
Woods Hole, MA 02543 USA
PHONE: 508-289-7435
EMAIL: jfur...@mbl.edu
http://www.mblwhoilibrary.org
----- Original Message -----
From: "Mark Diggory" <mdigg...@gmail.com>
To: "Dorothea Salo" <ds...@library.wisc.edu>
Cc: "Dspace Tech" <dspace-tech@lists.sourceforge.net>
Sent: Friday, January 23, 2009 3:37:11 PM GMT -05:00 US/Canada Eastern
Subject: Re: [Dspace-tech] rolling back a patch: database_schema_13-14.sql
I tend to agree with Dorothea on this one. I suspect it will be
difficult to roll back all the changes unless someone out there knows
how to magically unto completed transactions. If you can restore from
backup that would possibly be the safest decision. Otherwise,
reviewing the file, I see the following changes That I suspect would
duplicate table rows...
-- Migrate the existing DCTypes into the new metadata field registry
INSERT INTO MetadataFieldRegistry
(metadata_schema_id, metadata_field_id, element, qualifier, scope_note)
SELECT '1' AS metadata_schema_id, dc_type_id, element,
qualifier, scope_note FROM dctyperegistry;
-- Copy the DCValues into the new MetadataValue table
INSERT INTO MetadataValue (item_id, metadata_field_id, text_value,
text_lang, place)
SELECT item_id, dc_type_id, text_value, text_lang, place FROM dcvalue;
These will duplicate rows in the MetadataFieldRegistry and duplicate
copy DCValues into the MetadataValueTable. I assume that is where your
duplication is occurring.
I might also be concerned about your bistream sizes now with the
following update:
ALTER TABLE bitstream ADD COLUMN size_bytes BIGINT;
UPDATE bitstream SET size_bytes = size;
ALTER TABLE bitstream DROP COLUMN size;
Finally, I think if your using the ChecksumChecker, you might
encounter issues with duplicates in your checker tables caused by many
inserts into them as well.
If you haven't had any changes you need to maintain today, I would try
to recovre from a db backup instead of having to do surgery.
Mark
On Fri, Jan 23, 2009 at 12:21 PM, Dorothea Salo <ds...@library.wisc.edu> wrote:
> On Fri, Jan 23, 2009 at 1:34 PM, John Furfey <jfur...@mbl.edu> wrote:
>> I erred in applying the above patch to a 1.4 system, and the results are
>> that now there are duplicate metadata fields for each item view. Example:
>
>> Is there an easy way to rollback a patch, or is it better to restore the db
>> from a backup?
>
> Oh, man, I've done that. (Only on a test install, fortunately.) If
> there's an easy fix, I don't know what it is; I'd say restore from
> backup.
>
> Dorothea
>
> --
> Dorothea Salo ds...@library.wisc.edu
> Digital Repository Librarian AIM: mindsatuw
> University of Wisconsin
> Rm 218, Memorial Library
> (608) 262-5493
>
> ------------------------------------------------------------------------------
>
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________
> DSpace-tech mailing list
> DSpace-tech@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
>
--
~~~~~~~~~~~~~
Mark R. Diggory
Home Page: http://purl.org/net/mdiggory/homepage
Skype ID: mdiggory
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
