Re: sequential numbering across more instances
Re: sequential numbering across more instances
- Subject: Re: sequential numbering across more instances
- From: Alan Ward <email@hidden>
- Date: Fri, 15 Aug 2008 18:47:06 -0600
On Aug 15, 2008, at 6:24 PM, Chuck Hill wrote:
On Aug 15, 2008, at 1:48 PM, Mike Schrag wrote:
Sometimes the app is not the right level for solving the
problem. I do try to avoid things like this, but sometimes they
are the best solution.
Why would you choose this route rather than selecting from your
db's sequence generator from WO (assuming your db has sequences)?
I mean, if you're doing db-specific things anyway?
I think the goal is to avoid gaps in the sequence. Gappy solutions
are a dime a dozen. ;-) That is more easily done at the end of a
transaction at the database level. I _think_ an After Insert
trigger should avoid sequence gaps.
That would do it, yes. Have EOF insert the record with a null value
in the column and use a trigger (after insert) to assign the value
from a sequence.
Be aware though that you should not lock on that column or else
you'll run into optimistic locking failures if you subsequently
update any other
column before refetching the (now modified) EO.
Alan
Chuck
--
Chuck Hill Senior Consultant / VP Development
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40apple.com
This email sent to email@hidden
_______________________________________________
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