On Thu, Jan 22, 2009 at 4:30 PM, Barry Beattie wrote: > > mate, thanks for your interest and input.
No sweat. >> 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? ... > eg: child fails so roll back the Grandparent changes. Ah. Well then, you are screwed. :-)P >> 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) Let me repeat myself: you are scre-- :-) Seriously tho: hrm... what about passing a batch job to the WS itself? Some XML-RPC stuff I use lets you do a "multi"-command, which is basically just a batch of calls to run. Theoretically, that shouldn't be too hard of a deal to add to the the WS, but if they aren't in the spirit of "making things better, not just for one customer, but for all", you're still SOL. So, yeah, I guess you could do a push-pop stack type of deal to maintain state yourself, but, damn, it would all be pretty easy if you could get the WS folks to work with you. > anyhoo, many thanks for your help. appreciated. misery likes company? I loves me a good challenge. =] -- If a man's wit be wandering, let him study the mathematics. Francis Bacon --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
