Yes, I do want to tell them EXACTLY what to run. Both for Postgres
and Oracle. If Oracle has more steps, that's fine. We want to
make this documentation "question-proof" in a way. (As Dr. Suess'
books would write "Say what you mean, mean what you say".)
I want to make the documentation solid that we don't see the list
serve flooded with questions about the upgrade.
Thanks,
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 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
