I'm going to make one final post in this thread, since we didn't quite reach a conclusion.
Malcolm Tredinnick wrote: > As I mentioned to Collin at the code sprint in Portland, I think it'd be > a good idea to make sure we expose the ability to turn on auto-commit, > but I don't really like making it the default. In any case, providing > the ability that's can be controlled via, for example, a setting is > certainly the first step here. That's pretty independent of the whatever > the default might end up being. That's really the improvement needed to > #3460 at the moment -- separating adding functionality from changing the > default. Richard Davies wrote: > I think that we should try to write a patch which a) makes 'native > autocommit' a configuration option as suggested, and b) supports > transactions on top of the 'native autocommit' connection when explicitly > requested (the current 3460 patch doesn't, so parts of the test suite > currently fail when it is applied). Metajack wrote: > +1 from me So, do we agree that it makes sense for me to take the current 3460 patch and complete it in the manner which I described in http://groups.google.com/group/django-developers/msg/48500109ac5e514d ? I'd particularly like Malcolm to confirm if my description there matches his discussion with Collin. If we're agreed, then I'll take over ownership of that ticket from Collin (unless you want to do it, Collin?), and I'll add 'optional native autocommit' to the Django 1.1 features list. Cheers, Richard. ---- One technical point: When I started writing in this thread, I hadn't appreciated that rollback() and rollback_unless_managed() are used by Django outside explicit user-started transaction management in order to attempt to keep things consistent after failures. How do people think that we should handle these when 'native autocommit' is on? The options seem to be: a) Make them no-ops and accept the failures b) Work out which points they roll back to, and add explicit 'BEGINs' at those points --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
