Hi, I'm currently working on an application to « soft-delete » objects (mark them as deleted in the database, and mask them from the queries made using the default manager). https://github.com/makinacorpus/django-safedelete But it can't work well with GeoDjango the way managers are handled now (as GeoDjango needs to have its manager used for OneToOne & ForeignKey relationship, safedelete can't or it breaks everything).
I also had to dig a little to see how the managers currently works in Django. It seems that the documentation is unclear about it, and I have also seen that a lot of tickets were related to this issue : https://code.djangoproject.com/ticket/14891 https://code.djangoproject.com/ticket/13793 https://code.djangoproject.com/ticket/17746 This matters had also been discussed earlier on this ML, and some interesting ideas were raised, but nothing was done : https://groups.google.com/forum/#!topic/django-developers/vhKx9CLbNjQ I would really like to help, and try to submit a patch that would correct the issue. So, guidance would be welcome, as I don't want to submit a patch that would have design flaws, etc… I think some advices will also be needed in the future, as I am not really familiar with Django internals. For now, I think I would like to go on with having the ability to set custom managers for individual relations. What do you think about that ? (I wonder about backward compatibility, still…) Regards, Korantin Auguste. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. For more options, visit https://groups.google.com/groups/opt_out.
