Subject: | |
From: | |
Reply To: | |
Date: | Thu, 30 Jan 2003 18:48:34 -0800 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Wirt writes:
> CIUPDATE was designed to allow a user organization to add and drop
> indexes as they feel necessary, with no concern that they would
> affect their applications, something that is fundamentally impossible
> now with CIUPDATE off.
So the user is clever enough to buy Querycalc, and smart enough (or you've
suggested) to add an index to a dataset so that reporting can be done
faster, and capable of using Adager or editing the schema and manually
reloading the database to effect the change, and yet adding a single extra
DBUTIL command to this process is going to stop someone from doing it?
Since "adding and dropping indexes" is also "fundamentally impossible" in
Image without the use of a tool like Adager, how about if Adager were to
offer to set CIUPDATE to "ON" any time the user adds a path to a dataset?
G.
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
|
|