Thanks. Bill Tanzen also pointed out the resouce_type_id to me off list. I've been working quite a bit with the 3.1 database lately and didn't take in that part of the change in table structure.
Chris On 15-04-03 07:19 AM, helix84 wrote: > Hi Chris, > > I'm not sure I understand your problem. Since DSpace 5, you are > guaranteed unique rows in the metadatavalue table using the composite > key (resource_id, resource_type_id) where resource_type_id is one of > the constants: > https://github.com/DSpace/DSpace/blob/dspace-5_x/dspace-api/src/main/java/org/dspace/core/Constants.java#L20-41 > > In case I misunderstand, please provide an example that will help me > see the problem in this form: > epersongroup.eperson_group_id = 123 > community.community_id = 456 > ... > > > > Regards, > ~~helix84 > > Compulsory reading: DSpace Mailing List Etiquette > https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette ------------------------------------------------------------------------------ BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
