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
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to archive@mail-archive.com
