(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
Remove some old comments
Remove test tables
Remove sorttitle function
git-svn-id: http://scm.dspace.org/svn/repo/trunk@55 9c30dcfa-912a-0410-8fc2-9e0234be79fd
Community and Collection browse views remain views, but are no longer
dynamically ordered.
git-svn-id: http://scm.dspace.org/svn/repo/trunk@54 9c30dcfa-912a-0410-8fc2-9e0234be79fd
- Added schema file
- Add InitializeDatabase command line class
- Can now pass in "dspace.configuration" system property which will get
ConfigurationManager to load a specific configuration
- Added a simple log4j properties file for use during builds (e.g. when
executing InitializeDatabase)
- Changed a couple of INFO level logs to DEBUG in DatabaseManager
git-svn-id: http://scm.dspace.org/svn/repo/trunk@7 9c30dcfa-912a-0410-8fc2-9e0234be79fd