SF feature request #620658.
- Modified DB schema for items. Now items have a 'last_modified' property,
which is updated whenever the item is modified (obviously.) This date is
used for the harvesting.
- Optimised Item.java/DCType.java: Now, DCType.java loads in all DC types
up front so that Item.java does not have to do more queries to get the
elements and qualifiers. Greatly reduces number of SQL queries per harvest.
- Added upgrade script to set last_modified date for items that need them.
git-svn-id: http://scm.dspace.org/svn/repo/trunk@644 9c30dcfa-912a-0410-8fc2-9e0234be79fd
queried, and the table was large - sort_authors, sort_titles,
handles, resourcepolicy-objecttype & id, dcvalue-itemid, etc.
git-svn-id: http://scm.dspace.org/svn/repo/trunk@620 9c30dcfa-912a-0410-8fc2-9e0234be79fd
- Updated DB schema:
* New "subscription" table
* EPerson: renamed "active" to "can_log_in", and added "last_active",
"self_registered" and "sub_frequency" columns (unused right now, but
easier to make the changes at once)
- Updated EPerson object to reflect table changes, and callers of EPerson
object
- Removed MIT-only filters from web.xml
git-svn-id: http://scm.dspace.org/svn/repo/trunk@446 9c30dcfa-912a-0410-8fc2-9e0234be79fd
(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
This is expected to be used for the short term, and obsoleted by ingest
How to load the data:
* Load the schema definitions if not already present
* Load the registries if not already present
* Load this file, either via psql (\i FILE) or the InitializeDatabase class
* Create the Browse index, either via Ant target (setup_browse) or
via the InitializeBrowse class
git-svn-id: http://scm.dspace.org/svn/repo/trunk@68 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
