Re: locking and processes outside the transaction....

Five Cats said: > In message <c9n10g$gpd$1@news.xmission.com>, Obnoxio The Clown > <obnoxio@serendipita.com> writes >> >> >>BigBob said: >>> I need to lock a ROW in an Informix DB and hold onto that lock until >>> the end of a transaction. My first attempt at this was to begin work, >>> lock, etc. This worked great for the application itself. >>> >>> However, the problems arose in system testing we found some "external" >>> processes that update Informix tables "in" the transaction, but not >>> locked. They were prevented from doing so and we had to backout the >>> locking change. >>> >>> Is there any way to accomplish this? Lock a row, hold it and much >>> later, release it without impacting access to other tables in the same >>> transaction? >> >>Why "much later"? That's just really bad programming. > > Well yes it is - but sometimes it happens and has to be dealt with. Does it? I must have been doing something wrong all these years then. -- Bye now, Obnoxio "C'est pas parce qu'on n'a rien ' dire qu'il faut fermer sa gueule" - Coluche "Necrophilia means never having to say ... well, anything!" - Captain Pedantic "Ogni uomo mi guarda come se fossi una testa di cazzo" - Marco sending to informix-list