Re: Ensure an object is saved even when the atomic bock rollsback

> Den 08/05/2015 kl. 15.15 skrev Marc Aymerich : > > HI, > > I'm using atomic requests, but one of my views needs to save a model > regardless of wheter the current transaction rolls back or not. > > I'm confused about how to proceed with the current autocommit

Re: Ensure an object is saved even when the atomic bock rollsback

On Fri, May 8, 2015 at 6:43 PM, Marc Aymerich wrote: > > > On Fri, May 8, 2015 at 5:50 PM, Carl Meyer wrote: > >> Hi Marc, >> >> On 05/08/2015 07:15 AM, Marc Aymerich wrote: >> > I'm using atomic requests, but one of my views needs to save a model >> >

Re: Ensure an object is saved even when the atomic bock rollsback

On Fri, May 8, 2015 at 5:50 PM, Carl Meyer wrote: > Hi Marc, > > On 05/08/2015 07:15 AM, Marc Aymerich wrote: > > I'm using atomic requests, but one of my views needs to save a model > > regardless of wheter the current transaction rolls back or not. > > > > I'm confused about

Re: Ensure an object is saved even when the atomic bock rollsback

Hi Marc, On 05/08/2015 07:15 AM, Marc Aymerich wrote: > I'm using atomic requests, but one of my views needs to save a model > regardless of wheter the current transaction rolls back or not. > > I'm confused about how to proceed with the current autocommit behaviour. > Do I need to use a

Ensure an object is saved even when the atomic bock rollsback

HI, I'm using atomic requests, but one of my views needs to save a model regardless of wheter the current transaction rolls back or not. I'm confused about how to proceed with the current autocommit behaviour. Do I need to use a different db connection? or perhaps there is some way of telling