On Fri, Jun 1, 2012 at 1:46 PM, stuart.wood <[email protected]> wrote: > may have fixed this myself. I recently migrated the database and somehow the > sequencing got out of sync on the community2community table, the following > looks to have fixed it... > > SELECT setval('community2community_seq', (SELECT MAX(id) FROM > community2community)+1);
Glad you figured it out. In the future, you may use the provided script to update all sequences after such migrations: [dspace]/etc/postgres/update-sequences.sql In fact, you can run it even now in case some other sequences are wrong. Regards, ~~helix84 ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
