> That begs the question: how do the owners of the database expect you > to implement transactional integrity? Have they even thought about it? > Do they understand that it's a problem? I would try to tackle this at > source - with the people who own the DB and expose the web services.
well, the database is very tightly integrated into the application (create a new custom entity, publish it, and new db tables will appear for it, and references into other tables get written). the application exposes the webservices because most clients (large multi-million dollar installs with hunderds-of-seats working with tens of thousands of users: mining, govt, banking, etc) only ever expected to perform CRUD operations on single entities at a time, not roll up multiple entity writes in a single action. methinks this is either an oversight on their part - or - what we're asking of the system is too much customisation for it. > This is their problem since it affects any client users, not just you. yes, and on further investigation, this seems to be the case. There seems to be not a small number of clients affected by exactly this. what was the term used earlier? ... ah, yes ... "screwed" woe. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
