Re: Informix locking & transactions

BigBob said: > I need to lock a ROW in an Informix table and hold onto that lock until > the end of a transaction. During this transaction, 2 seperate Java > processes MIGHT start and want to update a table held in that > transaction before it is released. Is there any way to accomplish > this? > > Let me explain... Try again. :o) I really can't understand the problem -- are you using LOCK MODE (ROW) on all these tables? What ISOLATION LEVEL are you using? > An online application issues a "begin work" then opens a cursor with a > select for update going after a single row in a table (e.g. Table A). > The business requires that no one else be allowed to access 'child > tables' linked to that particular row until they back-out(rollback) or > complete the transaction (commit). This works well within the > application. > > However, the problems arose in system testing when we found some > "external" processes in Java that need to update a table (e.g. Table M) > "in" the transaction, but not the particular table locked (e.g. Table > A). Since Table M is held by the transaction, the Java processes are > prevented from doing the updates. > > So, I need to be able to "lock" a row in Table A but not release it > until the commit which could be after they access Table Z, but allow > the external Java processes to update Table M. > > Is this possible? Is there a different design that I could use? > Thanks in advance for the help! > -- Bye now, Obnoxio "C'est pas parce qu'on n'a rien ' dire qu'il faut fermer sa gueule" - Coluche "I'm trying to see things your way, but I can't get my head up my ass" - JCH "Ogni uomo mi guarda come se fossi una testa di cazzo" - Marco I went to the airport to check in and they asked what I did because I looked like a terrorist. I said I was a comedian. They said, "Say something funny then." I told them I had just graduated from flying school. -- Ahmed Ahmed sending to informix-list

Lock Mode is Row Isolation Level is Committed Read.