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

Bob Banks said: > Row level locking. OK, post the offending query, the explain plan for it, and the schema for the table with indexes. > ----- Original Message ----- > From: "Obnoxio The Clown" <obnoxio@serendipita.com> > To: "Bob Banks" <rwbanks@hotmail.com> > Cc: "Obnoxio The Clown" <obnoxio@serendipita.com>; > <informix-list@iiug.org> > Sent: Thursday, June 03, 2004 8:25 AM > Subject: Re: locking and processes outside the transaction.... > > >> >> Bob Banks said: >> > Thanks for the post. >> > >> > The problem isn't with Informix as it's doing the job. The problem is > that >> > while this database transaction is active/open, we have a Java process >> > that >> > needs to update one of the tables accessed in the transaction. The >> Java >> > process fails as that table is "in a transaction". >> > >> > Is there anyway around this? >> > >> > I realize you don't normally want to hold onto locks that long, but in >> > this >> > instance the business requires it remain locked until the user 'signs > off' >> > at the end at which time I can release the lock. >> >> It still doesn't work for me. :o) >> >> Are you using page or row level locking? >> >> > ----- Original Message ----- >> > From: "Obnoxio The Clown" <obnoxio@serendipita.com> >> > To: "BigBob" <rwbanks@hotmail.com> >> > Cc: <informix-list@iiug.org> >> > Sent: Thursday, June 03, 2004 3:57 AM >> > Subject: Re: locking and processes outside the transaction.... >> > >> > >> >> >> >> 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. >> >> >> >> -- >> >> >> >> 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 >> >> >> > >> >> >> -- >> >> 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 >> > -- 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