On Sun, Sep 19, 2010 at 11:41 AM, Alex Gaynor wrote:
> On Sun, Sep 19, 2010 at 10:28 AM, drakkan wrote:
> > in my opinion django should emulate "ON DELETE CASCADE" only on
> > database backends that doesn't support it, if you are using a database
>
On Sun, Sep 19, 2010 at 10:28 AM, drakkan wrote:
>
>
> On 17 Set, 15:38, Tobias McNulty wrote:
>> On Fri, Sep 17, 2010 at 8:27 AM, SmileyChris wrote:
>>
>> > On Sep 11, 1:12 pm, Tobias McNulty wrote:
On 17 Set, 15:38, Tobias McNulty wrote:
> On Fri, Sep 17, 2010 at 8:27 AM, SmileyChris wrote:
>
> > On Sep 11, 1:12 pm, Tobias McNulty wrote:
> > > I may be missing something, but queryset.delete() seems oddly implemented
On Fri, Sep 17, 2010 at 8:27 AM, SmileyChris wrote:
>
> On Sep 11, 1:12 pm, Tobias McNulty wrote:
> > I may be missing something, but queryset.delete() seems oddly implemented
> in
> > Django. It does a select to get all the IDs to be deleted, and
On Sep 11, 1:12 pm, Tobias McNulty wrote:
> Hi All,
>
> I may be missing something, but queryset.delete() seems oddly implemented in
> Django. It does a select to get all the IDs to be deleted, and then deletes
> them, in blocks of 100 I believe, by ID.
It's because
Hi All,
I may be missing something, but queryset.delete() seems oddly implemented in
Django. It does a select to get all the IDs to be deleted, and then deletes
them, in blocks of 100 I believe, by ID. Is there a reason it needs to do
this and/or is it overly complex to implement as a single