Hi Josh, > If so, that's rather problematic. The CTID is a physical pointer ID, > and as such can change out from under a current session if there are > concurrent updates. Using the CTID to grab rows could result in errors > or even seeing expired data.
Which means SCOPE would be something other than bestRowSession - and the bug on OOo side would be to use CTID for the given purpose nonetheless. @Zoltan: Care to submit an issue? Ciao Frank -- ORACLE Frank Schönheit | Software Engineer | frank.schoenh...@oracle.com Oracle Office Productivity: http://www.oracle.com/office --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@dba.openoffice.org For additional commands, e-mail: dev-h...@dba.openoffice.org
