> MS SQL Server uses a 'timestamp' column to check if a row has
> been altered since it was read. The equivalent in PostgreSQL
> seems to be the system column 'xmin'. However, the notes say
> 'You do not really need to be concerned about these columns,
> just know they exist.' Is it ok to use xmin
Frank Millman wrote:
> MS SQL Server uses a 'timestamp' column to check if a row has been
> altered since it was read. The equivalent in PostgreSQL seems to be
> the system column 'xmin'. However, the notes say 'You do not really
> need to be concerned about these columns, just know they exist.' Is
On Thu, Jan 13, 2005 at 11:49:00AM +0200, Frank Millman wrote:
> I have been reading up on 'optimistic concurrency control'.
>
> The following quote is taken from the on-line help for MS SQL Server 2000 -
> MS SQL Server uses a 'timestamp' column to check if a row has been
> altered since it wa
Hi all
I have been reading up on 'optimistic concurrency
control'.
The following quote is taken from the on-line help
for MS SQL Server 2000 -
"Optimistic concurrency control works on the
assumption that resource conflicts between multiple users are unlikely (but not
impossible), and a
