Re: multi user increment
Re: multi user increment
- Subject: Re: multi user increment
- From: Guido Neitzer <email@hidden>
- Date: Mon, 6 Feb 2006 16:45:26 +0100
On 06.02.2006, at 16:36 Uhr, Gino Pacitti wrote:
What about the holding of a value in a table and doing a raw row
fetch and if on committal there is a conflict alert user to change?
I haven't done this. but what about a single table for that and lock
the table (or the row) for a complete transaction of reading the
current value, incrementing it and writing back the new number. So
you won't need a handling for optimistic locking failures and
everything is wrapped in a single SQL transaction. But perhaps it may
block your applications in timeouts, if there is a lot of concurrent
traffic for this feature ...
cug
--
PharmaLine, Essen, GERMANY
Software and Database Development
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden