I hit the same wall when writing a loaddata variant to load json on geodjango. I couldn't find a solution either. :(
I hope someone can give us light in this regard. Ariel. On Feb 12, 2008 5:34 PM, Jeremy Dunck <[EMAIL PROTECTED]> wrote: > > Are people using the transaction.commit_manually decorator? > > I thought I understood it, but just learned that I don't. > > I'm using the transaction middleware and that's good for most of my > purposes. > > I have another function called from lots of different views, and > within that function, I wanted to isolate the general transaction > condition from the connection/queries I need to run from that > function. > > The goal here is to have a function that can run successfully when the > calling view (or anything else in the request cycle) had a SQL error. > Or vice versa, if an error occurs in this function, I'd like to > isolate it from the calling view's functionality. > > Anyway, I thought commit_manually set up a nested transaction, but > apparently it doesn't. > > So, if you're using it, can you explain how it's been useful to you? > I'd like to use it correctly. :) > > -Jeremy > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
