Re: locking a row from JDBC - Mailing list pgsql-jdbc

From Joshua Daniel Franklin
Subject Re: locking a row from JDBC
Date
Msg-id Pine.LNX.4.44.0211211328090.30905-100000@iocc.com
Whole thread Raw
In response to Re: locking a row from JDBC  (Barry Lind <blind@xythos.com>)
List pgsql-jdbc
Thanks John and Barry, as you have discovered I am new to SQL as
well. "SELECT ... FOR UPDATE" is what I was looking for.

On Thu, 21 Nov 2002, john guthrie wrote:

> my quick "i haven't looked it up so i amy be wrong" answer is that you
> can use "select for update"
>
> --
> john guthrie
> jguthrie@psynapsetech.com (was jguthrie@air.org)

On Thu, 21 Nov 2002, Barry Lind wrote:

> There isn't really anything specific jdbc does with locking.  You need
> to understand the locking behavior of the standard SQL commands you can
> issue through jdbc.  In addition to INSERT and UPDATE, I think the one
> you will find most useful is the SELECT ... FOR UPDATE command.  Check
> out the regular postgres docs for information on locking and the
> behavior of these sql commands.
>
> --Barry
>
> Joshua Daniel Franklin wrote:
> > I am rather new to JDBC and am trying to build a small java
> > application that will be used by a few people here. I have it
> > working in a single-user mode, but I would like to be able
> > to use some sort of locking on rows that are being edited
> > to make it multi-user safe. A quick google search did not turn
> > up anything interesting. Does anyone have any suggestions?
> >
> > Thanks.
> >
> > Joshua Daniel Franklin
> >
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 6: Have you searched our list archives?
> >
> > http://archives.postgresql.org
> >
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>

--
Joshua Daniel Franklin
Network Administrator
IOCC.COM



pgsql-jdbc by date:

Previous
From: Barry Lind
Date:
Subject: Re: locking a row from JDBC
Next
From: Nic Ferrier
Date:
Subject: Re: streaming result sets: progress