On Aug 15, 2008, at 09:55, Ondřej Čada wrote:
Hi all,
I've just bumped into a need to maintain a sequential numbering of
database rows, which are created by more concurrent WO application
instances.
If you just need a unique identifier for a row, you could use the
primary key value easily, so I am guessing that is not what you need.
So, could you elaborate on this a bit? What kind of a sequence is it?
Do the users need to provide values, or can they be auto generated?
In short, what are you trying to do?
Whilst I can think of a number of possible solutions, I'd like to
ask for your experience before implementing one? Strangely enough I
haven't done this yet, and thus can't well estimate the advantages
and disadvantages of different possible approaches (locking, UNIQUE
column, etc...) and their respective gotchas.
Thanks,
---
Ondra Čada
OCSoftware: [EMAIL PROTECTED] http://www.ocs.cz
private [EMAIL PROTECTED] http://www.ocs.cz/oc
_______________________________________________
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/flor385%
40mac.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
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 [EMAIL PROTECTED]