[
https://jira.duraspace.org/browse/DS-1578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hardy Pottinger updated DS-1578:
--------------------------------
Description: Running the clean_database ant target against an oracle
database still does not produce a "clean" database. A few tables are missed,
due to foreign key contraints, which would be helped by changing the order of
tables being deleted. Also, a few related sequences are not deleted, not sure
why. Manually cleaning up the DB (via drop table, drop sequence, etc.) has
always worked in the past. But, it should be something that we can do via a
script. One possible solution would be to maintain a drop_database.sql specific
to both PostgreSQL and Oracle, to work around any complexities due to running
the same SQL on different dialects of SQL. (was: Running the clean_database
ant target against an oracle database still does not produce a "clean"
database. A few tables are missed, do to foreign key contraints, which would be
helped by changing the order of tables being deleted. Also, a few related
sequences are not deleted, not sure why. Manually cleaning up the DB (via drop
ta
ble, drop sequence, etc.) has always worked in the past. But, it should be
something that we can do via a script. One possible solution would be to
maintain a drop_database.sql specific to both PostgreSQL and Oracle, to work
around any complexities due to running the same SQL on different dialects of
SQL.)
> improve clean_database ant target to work better with Oracle
> ------------------------------------------------------------
>
> Key: DS-1578
> URL: https://jira.duraspace.org/browse/DS-1578
> Project: DSpace
> Issue Type: Task
> Environment: DSpace on Oracle
> Reporter: Hardy Pottinger
> Assignee: Hardy Pottinger
> Fix For: 4.0
>
>
> Running the clean_database ant target against an oracle database still does
> not produce a "clean" database. A few tables are missed, due to foreign key
> contraints, which would be helped by changing the order of tables being
> deleted. Also, a few related sequences are not deleted, not sure why.
> Manually cleaning up the DB (via drop table, drop sequence, etc.) has always
> worked in the past. But, it should be something that we can do via a script.
> One possible solution would be to maintain a drop_database.sql specific to
> both PostgreSQL and Oracle, to work around any complexities due to running
> the same SQL on different dialects of SQL.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
