Hi, reading the "configuring Data Management Servic destination" chapter of the flex manual, i've discovered that flex handles alle changes as a unit, respecting the transactional aspect of the operations. But i've tried a lot of time to check if there's a real transaction and a real general rollback of more that one changes to the database. In all of my cases this is not true and there's always only a single rollback of the single problematic change and all the previous changes are committed.
Any idea? Thank you very much for any suggestions --- In [email protected], "fabio_sebastiano" <[EMAIL PROTECTED]> wrote: > > Hi all, > I've got a question about transactions with FDS and DataManagement > Service Assemblers. > I would like to know if that's possible to handle multiple changes on > dataBase records within the same transaction. > Usually FDS handle single actions when the user commit the changes, > performing the sequence of update-insert-delete using the updateItem, > deleteItem and createItem methods. > If there's a problem with one of this methods, the system rollback > only the problematic record change and persists all the previuos changes. > Do you know if there's a way to do alle the changes within the same > transaction, rolling back all the changes if there's a problem? > Is there something in DataManagament Services that i can use or > configure in order to obtain a real transactional assembler? > > Thank you very much, > > Fabio Sebastiano > DataSoftware S.r.l. > Corso Fiume 17 > 10091 Torino > Italy >
