Mike Kear wrote:
> What is going to happen is event type {a} happens (lets say it's a
> sale). That triggers a default action plan of umpteen things that
> have to follow based on that event, documents that have to be filed,
> people notified, approvals gained etc, then the the default plan has
> to be modified to allow for the specifics of this particular
> transaction.
>
> So the event has to trigger the generation of a whole heirarchy of
> maybe up to 50 things that have to happen, some of which rely on
> previous things being done
Would it be correct to say you have a table with X independent
hierarchies with about 50 elements per hierarchy with their own left and
right values, where you can identify which hierarchy an element belongs
to because they all reference the original event (the sale)? Because in
that case when you update a hierarchy you are only updating a limited
range of the total table. That really shouldn't pose any performance
problems for a well tuned database.
Jochem
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to
date
Get the Free Trial
http://ad.doubleclick.net/clk;203748912;27390454;j
Archive:
http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:312754
Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
