Hrm... is there anyway to mess with the order, such that if an update failed, you could halt processing there without leaving the DB between states?
Grandparent, parent, child, instead of the reverse, or some such? It's lame, but maybe something like that would "work"? You don't have any way to manually start a DB transaction, and then run the stuff, and then roll it back if it fails? Guess not, but maybe the DB has something that you could tap... That's all I got. :-) -- If a man will begin with certainties, he shall end in doubts, but if he will content to begin with doubts, he shall end in certainties. Francis Bacon On Thu, Jan 22, 2009 at 6:03 AM, Barry Beattie wrote: > > I know it's impossible, but I gotta come up with something... ... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CFCDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cfcdev?hl=en -~----------~----~----~----~------~----~------~--~---
