Hello,
The official coding period has started a week ago, therefore I guess a
progress report is in order.
As far as changes to the proposal are concerned, it seems there aren't
any. There haven't been any objections or other suggestions to improve
the proposal, other than the updatable primary
Minor correction: I placed Atomic.__exit__ to verify - the transaction is
commited every time *starting* on the second object (the third stack
printed in the previous post) - it happens at
https://github.com/django/django/blob/master/django/db/transaction.py#L288.
On Sunday, June 23, 2013
Hi again Russell,
I did a little digging. I'm not sure, but I may have uncovered the problem.
A transaction block (using `commit_on_success_unless_managed`) is entered
and exited during each fixture object loaded, due to the calls to the
aforementioned method that exist in various model
Done
https://code.djangoproject.com/ticket/20643
M.
Dne neděle, 23. června 2013 20:04:28 UTC+2 Baptiste Mispelon napsal(a):
>
> Hi,
>
> I believe you're right, this code is incorrect.
> Would you mind opening a ticket for this on
> https://code.djangoproject.com/newticket ?
>
> Thanks,
>
Hi,
I believe you're right, this code is incorrect.
Would you mind opening a ticket for this on
https://code.djangoproject.com/newticket ?
Thanks,
Baptiste
On 06/23/2013 05:29 PM, Michal Slįdek wrote:
Hello!
I tried to use following examples:
Hello!
I tried to use following examples:
https://docs.djangoproject.com/en/dev/topics/class-based-views/mixins/
import jsonfrom django.http import HttpResponseclass JSONResponseMixin(object):
response_class = HttpResponse
def render_to_response(self, context, **response_kwargs):
