Robert Tansley 35e9b51a53 Some database changes for dealing with concurrent ID generation problems. ...

(SF bug #495059)
- SQL file separated into database_schema.sql, for creating the schema,
  clean-database.sql, which removes tables, views etc. from an existing
  DSpace database, and update-sequences.sql which resets the ID generators,
  but is only used after an SQL dump which sets explicit primary keys.
- Sequences for primary key generation added to SQL schema
- SQL function "getnextid" added as an abstraction for access to those sequences
- Database manager now uses getnextid() SQL function to get IDs - this means
  other DB backends can hide ID generation specifics behind this
- Minor tweak to HistoryManager, which was accessing DB manager's in-memory
  ID generator directly - now it doesn't do this.
- Old, now unnecessary "reset ID generator" admin servlet/JSP removed


git-svn-id: http://scm.dspace.org/svn/repo/trunk@362 9c30dcfa-912a-0410-8fc2-9e0234be79fd

2002-09-09 19:44:33 +00:00

dspace

Some database changes for dealing with concurrent ID generation problems.

2002-09-09 19:44:33 +00:00

Description

(Official) The DSpace digital asset management system that powers your Institutional Repository

dspacejavaopen-accessopen-sourcerepositoryrest-api

BSD-3-Clause 523 MiB

Languages

Java 97.6%

XSLT 1.8%

HTML 0.2%

Rich Text Format 0.2%