Mike Matrigali wrote:
I was not aware of the alter table dependency check for offline
compress, this must be outside of store somehow - maybe something
tied to all alter table statements. It may make sense
to change online compress to hook up with whatever offline compress
is doing to make this happen.
Just testing the current system does not mean that future changes
won't break SUR. Unless we agree to change the contract on unlocked
RowLocations, then it still isn't right for code to depend on
an unlocked RowLocation not ever pointing to the wrong row - because
of the issue with truncate.
I would prefer if the store would be able to tell that a RowLocation has
become invalid instead of trying to prevent it from ever pointing to the
wrong row.
--
Øystein
