Thanks. But the more important question is how to use commit_on_success with class based view?
On Feb 16, 1:52 am, 赵帅 <rostin...@gmail.com> wrote: > The commit_on_success decorator only garrentees that one commit is done > when no exception is raised from the function and rollback if there is any . > You have to ensure on your own hand the values in the two tables are equal. > > 2012/2/15 Yann <yann.l....@gmail.com> > > > > > > > > > Hi, > > > In a class view, I am trying to modify two instances of different > > models. There are some identical data stored in both tables. They > > should really be the same in any circumstance . > > > Should I use "@commit_on_success"? > > > If I should, how should i use it for the class based view? > > > Should I do something like this? > > > class CreateSomethingView(CreateView): > > > "" > > "" > > @method_decorator(transaction.commit_on_succes) > > def post(self): > > "" > > > -- > > 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 > > django-users+unsubscr...@googlegroups.com. > > For more options, visit this group at > >http://groups.google.com/group/django-users?hl=en. -- 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 django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
