On Fri, Jan 8, 2010 at 7:17 AM, j...@jeffcroft.com wrote:
> With MultiDB, it's now essential that custom model save methods accept
> the "using" keyword argument. However, the docs explicitly suggest a
> signature like:
>
> def save(self, force_insert=False, force_update=False):
>
> (You can see t
On Thu, Jan 7, 2010 at 5:25 PM, j...@jeffcroft.com wrote:
>> Are you sending from other email addresses? I only see a few
>> occurrences of j...@jeffcroft.com on django-dev, and I haven't seen
>> you get destroyed. :-/ Sucks that you feel that way.
>
> The destruction tends to come via Twitter.
> Are you sending from other email addresses? I only see a few
> occurrences of j...@jeffcroft.com on django-dev, and I haven't seen
> you get destroyed. :-/ Sucks that you feel that way.
The destruction tends to come via Twitter. :)
I was half-joking, it's not a big deal.
--
You received thi
On Thu, Jan 7, 2010 at 5:17 PM, j...@jeffcroft.com wrote:
...
> I would suggest the docs ought to instruct users to use a signature
> like:
>
> def save(self, *args, **kwargs):
Sounds reasonable to me.
> I will now duck and cover, as I tend to get destroyed anytime i say
> anything at all in thi
With MultiDB, it's now essential that custom model save methods accept
the "using" keyword argument. However, the docs explicitly suggest a
signature like:
def save(self, force_insert=False, force_update=False):
(You can see this here, for example:
http://docs.djangoproject.com/en/dev/topics/db/m
