Essentially, you want a compare-and--swap instruction for a database?
Have you considered using memcached atomicity (add and cas) to handle this
kind of thing? It might get pretty elaborate, but with just a cursory
thought seems doable.
-peter
On Sat, Aug 6, 2011 at 9:59 PM, Steven Cummings wrot
FWIW: we are successfully using Ned's fix on top of 1.2.5 today. -peter
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to
See ticket 15840.
On Thu, Apr 14, 2011 at 9:25 AM, Russell Keith-Magee <
russ...@keith-magee.com> wrote:
> On Thu, Apr 14, 2011 at 8:16 PM, Peter Portante
> wrote:
> > Looking at line 153 of django/views/decorators/http.py (rev [15927]),
> > I just see "return
+1 from the Tabblo group remnants.
On Thu, Apr 14, 2011 at 8:41 AM, Ned Batchelder wrote:
> Does anyone else have any opinions on a direction forward to fix this
> problem? At the very least I'd like to make a doc patch for 1.3.1 that
> explains the fragility.
>
>
--
You received this message
Looking at line 153 of django/views/decorators/http.py (rev [15927]),
I just see "return inner". Is there a particular reason why it should
not be: "return wraps(func, assigned=available_attrs(func))(inner)"?
--
You received this message because you are subscribed to the Google Groups
"Django de
