On Sat, Dec 5, 2009 at 10:56 AM, Russell Keith-Magee
wrote:
> On Sat, Dec 5, 2009 at 5:35 AM, Ryan K wrote:
>>
>> I hope I'm not missing something glaringly obvious but the idea would
>> be that an option in the Django instance's settings would enable this
>> feature (or maybe as a decorator for
On Sat, Dec 5, 2009 at 5:35 AM, Ryan K wrote:
>
> I hope I'm not missing something glaringly obvious but the idea would
> be that an option in the Django instance's settings would enable this
> feature (or maybe as a decorator for each model or explicitly giving
> the model a special manager).
St
Correction: "Surely this would be much slower but for situations where
write's are very [IN]frequent it's okay to pay."
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
Okay, thank you for clarifying the problem. I admit that I am least
familiar with the database operations as they are implemented in
Django so I will read the relevant code and see if indeed something
_can_ be done. This is not a bug at all but I think it raises a valid
question. Signals are really
On Fri, Dec 4, 2009 at 3:44 PM, Ryan K wrote:
> Sorry for the confusion but I sent the original link from my mobile
> handset which isn't great for copying/pasting/etc.
In future, could I please ask you to consider that when you send a
message to django-developers, it arrives in over 5000 mailbox
Sorry for the confusion but I sent the original link from my mobile
handset which isn't great for copying/pasting/etc.
In another post, we were discussing the issue of ManyToMany updates
[1] and how the signal handler for a model X that has a
ManyToManyField to Y will _not_ have an updated Y. It's
On Fri, Dec 4, 2009 at 10:23 AM, Ryan K wrote:
> This message is in regards to the patch on Ticket 5390 (http://
> code.djangoproject.com/ticket/5390). I know that the period for
> changes is closed
The period for changes isn't closed at all - we're in the feature
development phase until Dec 22 [
This message is in regards to the patch on Ticket 5390 (http://
code.djangoproject.com/ticket/5390). I know that the period for
changes is closed but why shouldn't the current API just work. It
seems like a special case is being treated very differently but since
there relation is already implied i
