This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
How (if at all) are transactions supported on AWS SimpleDb. I understand that LightSpeed runs all of its persistence changes on a UOW in the scope of a transaction, but SimpleDb does not (natively) support transactions. Is LightSpeed taking responsibility for managing the rollback? If so, I imagine that this could be possible in the fetch-data-to-client-then-change-it-then-commit-it scenario (because the client/LightSpeed has the original data and can create the rollback commands on the fly). But what about scenarios in SimpleDb where LightSpeed is used to update all data matching a condition without first pulling that data client-side? What is the update fails (for some reason) part way through a huge number of remote records? SimpleDb is not (itself) transactional so each row update is committed separately. Does a LightSpeed transaction work in this context? Is my question clear? Any thoughts are appreciated. |
|
|
|
|
As you note, SimpleDB does not support transactions. We don't attempt to implement transactions in the LightSpeed layer. So if you save multiple changes in a batch then it's possible that some of them will commit but not others. We will not attempt to roll back changes. So basically the answer is that no, transactions don't work on SimpleDB, in any context. |
|
|
|
