[ http://issues.apache.org/jira/browse/DERBY-1067?page=comments#action_12369194 ]
Andreas Korneliussen commented on DERBY-1067: --------------------------------------------- > Suresh Thalamati commented on DERBY-1067: > ----------------------------------------- > > This patch seems to do something special for in-place compress making a > row location invalid, how is in-place compress invalidating a row location > diffent from say : > > 1) a drop table > 2) compress(SYSCS_COMPRESS_TABLE), that copies rows to a new container. > This is different because we are not trying to guarantee that a RowLocation is valid from any container, only from the container it is being used from. If a container is dropped, a cursor which has an open scan against it should fail. For holdable cursors, this should fail when trying to reopen the dropped container after a commit. I think this logic already is in place in Derby. > support holdable Scrollable Updatable Resultsets > ------------------------------------------------ > > Key: DERBY-1067 > URL: http://issues.apache.org/jira/browse/DERBY-1067 > Project: Derby > Type: Sub-task > Reporter: Andreas Korneliussen > Assignee: Andreas Korneliussen > Attachments: DERBY-1067.diff, DERBY-1067.stat > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
