On 8/24/07, Gábor Farkas <[EMAIL PROTECTED]> wrote:
>
> or, to turn this into more constructive discussion, what's the preferred
> thing to do, when someone does not get an answer to such a 'design
> decision needed' mail? should he wait more than i waited before he
> re-sends his question? how
Russell Keith-Magee wrote:
> On 8/23/07, Gábor Farkas <[EMAIL PROTECTED]> wrote:
>> hi,
>>
>> i posted this one week ago, could someone with commit access please
>> respond to it?
>
> If we're haven't addressed these tickets, it's not because we don't
> want to - we have just had other
hi,
i posted this one week ago, could someone with commit access please
respond to it?
thanks,
gabor
Gábor Farkas wrote:
> hi,
>
> when django deletes an object (using the object's delete() method),
> then all related objects are also deleted.
>
> this is not always a good thing.
>
>
On 16.08.2007., at 11:42, Gábor Farkas wrote:
> 1. create a non-recursive delete-method (either by adding a
> boolean-argument to Model.delete(), or by creating a new method)
>
> 2. make Model._collect_sub_objects into a documented non-private
> method.
That's a big +1 from me (for what is
hi,
when django deletes an object (using the object's delete() method),
then all related objects are also deleted.
this is not always a good thing.
there are various approaches to solve this, like:
http://code.djangoproject.com/ticket/1007
and
http://code.djangoproject.com/ticket/2288
,
but
