Jim,
The problem was this -
They have a view which they use to populate a list which:
can be edited and reordered.
As a result of reordering - when one row is assigned a new order - the reset
of the rows automatically get an update.
These changes are then sent to another area that in turn - passes it back to
oracle. It is not a matter of updating one table - so the idea of making the
view updateable does not solve the problem...
The goal was to be able to take edited data - useing a sql statement to have
the modifed data in the right order - running it into an array - and then
passing that array to a separate procedure.
Ultimately, the problem was solved by creating an index on the view and
ordering based on the sequence column - which has been modified. Then, by
scanning the table - the array could be created - with modifed values in the
right order.
IMO - its one of those things you could call one way or another as to
whether it is a bug. We found a workaround - so it is not a big deal.
< JVP >
Jim McGinnis wrote:
I see the names in upper case. Which is what I would expect since we've
got table buffering - right?
Issue TABLEUPDATE(.T.) and a new SQL shows lowercase.
< JVP >
john.v.petersen AT comcast DOT net
©2003 john.v.petersen |
