Larry,
Thanks. That should not be a problem to document. Since I have no
Oracle installation here
or have Oracle experience, I can't really write a lot. But, what I
can ask is if it is possible
to put into steps what you just said below. (key strokes, <enter>,
etc.) Manual steps shouldn't
be a problem. An example of those steps makes it perfect for the
user. So, even a
hypothetical approach could work. Those familiar with Oracle will
have a good grasp of its
issues--I hope.
Documentation in the html environmental is limitless. In the paper
world, it's only limited by
the amount of reams we have at our desk. All in all, the issue
present before us is insignificant
in the amount of paper that needs to be produced.
Jeffrey Trimble
System LIbrarian
William F. Maag Library
Youngstown State University
330.941.2483 (Office)
[email protected]
http://www.maag.ysu.edu
http://digital.maag.ysu.edu
"I must not fear. Fear is the mind-killer.
I will permit it to pass over me and through me..."
--Litany against fear....
On Nov 17, 2009, at 3:36 PM, Larry Stone wrote:
The problem is, those final steps for Oracle are to rename some
constraints to predictable names, from the random names they were
originally given by Oracle. There is no way that Andrea and I could
figure out, in Oracle, to change those names automatically -- the
admin-level SQL (DDL) to do it does not allow values from embedded
queries. It *could* probably be done with PL/SQL, or external
scripting, but we don't know the former and have no time to do the
latter, so it remains a manual effort: You run a query to get the
names, and then construct some commands to change them. It's another
beesting in the tsunami of pain that is running DSpace on Oracle.
If anyone has time to spare to implement an automated script, I'll be
happy to tell them more about the problem, or just look at the upgrade
script in the 1.6 source (relative path is dspace/etc/oracle/
database_schema_15-16.sql).
-- Larry
On Nov 17, 2009, at 1:52 PM, Sands Fish wrote:
On Nov 16, 2009, at 2:59 AM, Andrea Bollini wrote:
1) yes, you need to run an update sql script dspace/[postgres|
oracle]/
please put a notice for the oracle users like this: Please note
that the last 3 rows of the output of the sql script will be
additional queries to run against your db. They are need to make
changes to some foreign key definition, look to the comments inside
the sql script for additional information.
Documentation suggesting the user go digging in a SQL script for
additional information seems a bit unfriendly to me. Any reason we
couldn't just copy the additional information into the documentation?
--
sands fish
Software Engineer
MIT Libraries
Technology Research & Development
[email protected]
E25-131
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008
30-Day
trial. Simplify your report design, integration and deployment - and
focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
