Re: basic pg lock question - Mailing list pgsql-general

From Alban Hertroys
Subject Re: basic pg lock question
Date
Msg-id 4201F406.9000601@magproductions.nl
Whole thread Raw
In response to Re: basic pg lock question  (Scott Marlowe <smarlowe@g2switchworks.com>)
Responses Re: basic pg lock question
List pgsql-general
Scott Marlowe wrote:
> Method 2 often provides all the protection you need and is quite easy to
> program.  You basically do something like:

To use this to prevent simultaneous inserts of the same data (for
example if two employees try to insert the same contact into the DB), I
suppose you could use a constraint (before insert) that checks that
there is no data matching the md5 checksum, right?

--
Alban Hertroys
MAG Productions

T: +31(0)53 4346874
F: +31(0)53 4346876
E: alban@magproductions.nl
W: http://www.magproductions.nl

pgsql-general by date:

Previous
From: Carlos Costa
Date:
Subject: Re: Problem with the sequence
Next
From: PFC
Date:
Subject: Re: basic pg lock question