Hi all,
We are running Dspace for some years now, started at Dspace 1.1. When I export
the item table, order of the columns is last_modified after owning_collection.
CREATE TABLE item (
item_id integer NOT NULL,
submitter_id integer,
in_archive boolean,
withdrawn boolean,
owning_collection integer,
last_modified timestamp with time zone
);
COPY item (item_id, submitter_id, in_archive, withdrawn, owning_collection,
last_modified)
However in the database_schema.sql for Dspace 1.4.2 the table is created in
different order
CREATE TABLE Item
(
item_id INTEGER PRIMARY KEY,
submitter_id INTEGER REFERENCES EPerson(eperson_id),
in_archive BOOL,
withdrawn BOOL,
last_modified TIMESTAMP WITH TIME ZONE,
owning_collection INTEGER
);
Because I'm migrating the Postgresql database to Oracle, I'm dumping the data
as INSERT commands with explicit column names. That ensures data are entered
into the correct column.
INSERT INTO item (item_id, submitter_id, in_archive, withdrawn,
owning_collection, last_modified) VALUES (397, 91, 0, 1, 3, '2005-11-01
16:42:01.19+01');
Is it safe to assume that the difference in column order will not affect the
functioning of Dspace?
Best wishes,
Francis
------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
