Re: basic pg lock question

From: Alban Hertroys <alban(at)magproductions(dot)nl>
To: Scott Marlowe <smarlowe(at)g2switchworks(dot)com>
Cc: rschumeyer(at)ieee(dot)org, pgsql-general(at)postgresql(dot)org
Subject: Re: basic pg lock question
Date: 2005-02-03 09:51:02
Message-ID: 4201F406.9000601@magproductions.nl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)magproductions(dot)nl
W: http://www.magproductions.nl

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message PFC 2005-02-03 10:10:06 Re: basic pg lock question
Previous Message Carlos Costa 2005-02-03 09:45:20 Re: Problem with the sequence