I found this quite interestine discussion:
http://groups.google.com/group/django-developers/browse_thread/thread/166752daf5c96499/007ff42d83ac60c0

my opinion is close to Russell Keith-Magee opinion there. It looks
like a lot of effort was done just to conform django with small number
of databases.
This is not so but idea from some point of view, but losing efficient,
tested methods of handling deletes by db backends seems to be a great
loss for me.

Isn't possible to implement this as a sort of fallback mechanism 'if I
can relay on DB deleteing policy then I use it, otherwise Django
machinery created for that is enabled'?

Or amybe there is some workaround to make this work more efficient I'm
missing at the momment?

Regards,
Lukasz

On 29 Kwi, 02:17, Christophe Pettus <x...@thebuild.com> wrote:
> On Apr 28, 2010, at 4:36 PM, dzida wrote:
>
> > "When Django deletes an object, it emulates the behavior of the SQL
> > constraint ON DELETE CASCADE --
> > in other words, any objects which had foreign keys pointing at the
> > object to be deleted will be deleted along with it. ",
> > which is something I really want - but performed in shorter time.
>
> I'm a bit surprised Django does this.  Is there a reason that Django  
> re-implements ON DELETE CASCADE for databases that support it?
>
> --
> -- Christophe Pettus
>     x...@thebuild.com
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Django users" group.
> To post to this group, send email to django-us...@googlegroups.com.
> To unsubscribe from this group, send email to 
> django-users+unsubscr...@googlegroups.com.
> For more options, visit this group 
> athttp://groups.google.com/group/django-users?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Reply via email to