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, ,
etc.) Manual steps shouldn't
be
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 d
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 so
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. Th
Hi Jeffrey,
I try to help, these are some personal note about 1.5->1.6 migration...
pretty far to be complete!
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
I need a little assistance in making sure our directions for upgrading
a current installation
of DSpace 1.5 to 1.6 are going to be correct. As I start to code the
documentation this week,
here are the list of issues I need assistance with.
PRAENOTANDA: I have not attempted to upgrade any of
