Re: unlock Select for update - Mailing list pgsql-general

From jose antonio leo
Subject Re: unlock Select for update
Date
Msg-id KAEFLIDKHEJNPPKOLGHMCEIDCPAA.jaleo8@storelandia.com
Whole thread Raw
In response to Re: unlock Select for update  (Martijn van Oosterhout <kleptog@svana.org>)
Responses Re: unlock Select for update
List pgsql-general
Yes...
It is a web system. I Send part of code and explain in it.

JSP1
<jsp:useBean id="beanOfe" scope="session" class="eurocash.ManOfe"/> This
useBean instance ManOfe and connect to DB.

The user select a row to update and the jsp call the method
consultaTransaccional
    beanOfe.consultaTransaccional(hae) //call the method consultaTransaccional
of ManOfe


JSP2
<jsp:useBean id="beanOfe" scope="session" class="eurocash.ManOfe"/> This
useBean instance ManOfe and connect to DB.

The user update the row and submit. the jsp call to method modifica...

    beanOfe.modifica(hae) //call the method modifica of ManOfe




CLASS
public class ManOfe {
     public UtilBD utilBD = new UtilBD(); // connect to DB

  public Vector consultaTransaccional ( HOfe hOfeParam )
    {
      Vector vHOfe = new Vector();
      hOfe.utilBD.inicioTransaccion();                    //init transacstion
      vHOfe = hOfe.consultaForUpdate( hOfeParam );        //execute select for
update. Lock the rows.
      return (vHOfe);                            //return to jsp2
    }

    public HOfe modifica ( HOfe hOfeParam )
    {
      hOfeReturn = hOfe.modifica( hOfeParam );   // update the row locks
before
      hOfe.utilBD.finalTransaccion();         //end transaction, unlock row.
      return (hOfeReturn);
    }

}

In this system if the web user close your browser the row keeps blocked.

I hope that you understand to me






-----Mensaje original-----
De: Martijn van Oosterhout [mailto:kleptog@svana.org]
Enviado el: martes, 11 de marzo de 2003 10:01
Para: jose antonio leo
CC: Neil Conway; pgsql-general; Bruce Momjian
Asunto: Re: [GENERAL] unlock Select for update


On Tue, Mar 11, 2003 at 09:10:21AM +0100, jose antonio leo wrote:
> Unfortunately In my aplication this non occur . When the client
disconnects
> the row keep blocked and then I have kill the process manually for
unlocked
> the row.
>
> You know why it happends?

You're obviously doing something wrong, since if the client disconnected,
then there would be nothing to kill. You'll need to explain more about your
system before we can help you.

> -----Mensaje original-----
> De: Neil Conway [mailto:neilc@samurai.com]
> Enviado el: lunes, 10 de marzo de 2003 19:05
> Para: jose antonio leo
> CC: Bruce Momjian; pgsql-general
> Asunto: RE: [GENERAL] unlock Select for update
>
>
> On Mon, 2003-03-10 at 12:15, jose antonio leo wrote:
> > Sorry, I explain more...
> > I have got a aplication that it do maintenance of DB, One user are
> updating
> > a row locked for a select for update and this user switch off your pc
and
> he
> > leaves the row locked.
>
> When the client disconnects, any uncommitted transaction (if any) will
> be aborted, so the lock will be released.
>
> Cheers,
>
> Neil
>
> --
> Neil Conway <neilc@samurai.com> || PGP Key ID: DB3C29FC
>
>
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org

--
Martijn van Oosterhout   <kleptog@svana.org>   http://svana.org/kleptog/
> Support bacteria! They're the only culture some people have.


pgsql-general by date:

Previous
From: "shreedhar"
Date:
Subject: server closed the connection unexpectedly
Next
From: Martijn van Oosterhout
Date:
Subject: Re: unlock Select for update