I'm the author of #16611 ticket and after some consideration I also think
that proxy models are the way to go for such customizations.
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To view this discussion on the web visit
https://groups
There's a related, ongoing discussion here:
http://code.djangoproject.com/ticket/13906
It looks like the general attitude is that MySQL backend should switch to
READ COMMITED isolation level,
which would be the simplest solution.
Tomasz
--
You received this message because you are subscribed t
W dniu poniedziałek, 9 maja 2011, 19:05:17 UTC+2 użytkownik SleepyCal
napisał:
>
> Hi guys,
>
> I spent literally *months* trying to find the best way to resolve this
> situation. (...)
>
Have you checked my StackOverflow answer I linked in the top post? It
*completely* removes the problem for
W dniu sobota, 7 maja 2011, 20:03:40 UTC+2 użytkownik David Cramer napisał:
>
> Would it help (in PG-world) at least if the selects where in
> savepoints as well?
>
In case you asked me - I don't know, I don't use PG on a daily basis...
Anyway, let me list some possible solutions to launch the
I think that get_or_create is still broken, despite this fix:
http://code.djangoproject.com/ticket/6641
The details, along with a working solution, are in my answer here:
http://stackoverflow.com/questions/2235318/how-do-i-deal-with-this-race-condition-in-django/2235624#2235624
I'm not sure if t
