Yarek Kowalik <[email protected]> writes: > 1. Transactions. The current implementation of the Elephant store > does not do transations in the sense that Weblocks expects them. The > methods BEGIN-, COMMIT- and ROLLBACK-TRANSACTION don't do anything. > You can very easily find yourself in an inconsistent state if you > forget that fact > ... > I think in the case of Elephant it would make sense to make start/ > commit/rollback transactions to throw back an error immediately, to
It will be harder to forget when elephant-new-transactions is applied, as they will signal errors. I will apply it to dev when someone tests it and says that it works. Try it out from experimental-queue. > which may mean I may have to fallback on CLSQL (with per-thread > connection pooling from svg). http://weblocks.lighthouseapp.com/projects/18897-weblocks/tickets/61 > Also, the notion of a transaction hook around an action is a useful > one and perhaps should be ported to other stores, perhaps disabled > with a proper key to open-store. You can define your own request hooks for various times. -- I write stuff at http://failex.blogspot.com/ now. But the post formatter and themes are terrible for sharing code, the primary content, so it might go away sooner or later. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "weblocks" 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/weblocks?hl=en -~----------~----~----~----~------~----~------~--~---
