mate, thanks for your interest and input. > 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?
I'm concerned that something could fail anywhere in the process. > Grandparent, parent, child, instead of the reverse, or some such? eg: child fails so roll back the Grandparent changes. > 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? the database is off limits for us to insert/update data. They expose (these single) webservices instead - one set per entity (in our case a child, parent or grandparent) > That's all I got. :-) yeah, I'm coming up short here too. anyhoo, many thanks for your help. appreciated. misery likes company? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
