informed him about the ORM and at that point he
shook his head and said sorry cant help ya.
Trust me, the DB design is not the issue here.
Cheers,
Zach
On Dec 11, 11:49 am, oggie rob <[EMAIL PROTECTED]> wrote:
> On Dec 10, 6:25 am, AcidTonic <[EMAIL PROTECTED]> wrote:
>
&g
I believe any kind of delete will also clobber any models linked to or
from the object getting deleted.
One work around was to implement delete() on the model which nulls the
relationships first. That works except querysets with more than
one instance will NOT call the custom delete() method
; was happening either.
>
> Time to monkey-patch QuerySet's delete() method :)
>
> (I'm also a bit curious as to how its handling cascades in MySQL when
> it's not looping through each object)
>
> On Dec 10, 12:43 pm, "Karen Tracey" <[EMAIL PROTECTED]>
jango patch/hack/fix as opposed to my code needing a change?
I appreciate the prompt responses guys.
Zach
On Dec 10, 12:11 pm, "Jacob Kaplan-Moss" <[EMAIL PROTECTED]> wrote:
> On Wed, Dec 10, 2008 at 11:05 AM, AcidTonic <[EMAIL PROTECTED]> wrote:
> > Frankly its as simp
arly always
> encouraged. :)
>
> -Joey
>
> [1]http://code.djangoproject.com/ticket/7539
>
> On Wed, Dec 10, 2008 at 07:25, AcidTonic <[EMAIL PROTECTED]> wrote:
>
> > Currently the cascading delete functionality requires many users to
> > change how their app works slightly
Currently the cascading delete functionality requires many users to
change how their app works slightly to accommodate this "feature".
I'm curious how people are disabling or working around this aspect of
django.
I've heard many people are implementing custom delete() methods on the
model class.
