Flemming Frandsen wrote: > > [EMAIL PROTECTED] wrote: > > (1) the statement "SELECT ID FROM My_Table WHERE > Secondary_Key = ?" is prepared and > > (probably) executed > > (2) the statement "UPDATE My_Table SET Other_Column = ? > WHERE Primary_Key = ?" is executed > > from another thread (presumably using the same JDBC > DataSource), modifying a boolean > > column with no index or constraint on it > > (3) the ResultSet of the statement (1) is examined and > found to be empty. > > This is my guess: > > The #2 statement grabs a lock on the row preventing it from > showing up > in the resultset.
Nice idea, but SAP DB will wait for the release of that lock, not just skip the locked row(s). Elke SAP Labs Berlin > Regards Flemming Frandsen - http://dion.swamp.dk > PartyTicket.Net co founder & Yet Another Perl Hacker > > _______________________________________________ > sapdb.general mailing list > [EMAIL PROTECTED] > http://listserv.sap.com/mailman/listinfo/sapdb.general > _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
