Indeed! Perhaps nobody thought anyone would ever override the delete()
method...
I'm not sure why the strategy is to gather together all the related
objects and then do the SQL rather than call the delete() method on
each of them. Perhaps its more efficient. Perhaps it avoids possible
loops where
spacedman wrote:
> So I'd say you weren't doing something terribly wrong, but it might
> not be a bug either. If this behaviour is desirable (and I cant see why
> it isn't) then it needs a bit of rewriting...
Reading the documentation and this mailing list, I came to a silly idea
that django'
Viktor wrote:
> But when I delete a round, with round.delete(), all games conected with
> that round are also deleted, but the Score table isn't updated, that is,
> the delete method from the game objects is not called?!?!
Looking at the code I see that when an objects is .delete()d all the
rel
3 matches
Mail list logo