Re: Added signals that runs when adding an object to a Many-To-One relation

were implemented and your code > listened to that, there would be no need to add or listen to a > Manager.add() signal because it uses QuerySet.update() or QuerySet.save(). > > On Monday, February 6, 2017 at 2:17:28 PM UTC-5, Oskar Persson wrote: >> >> Yes, my PR does just

Re: Added signals that runs when adding an object to a Many-To-One relation

rySet.update(). For the update() signal to > process objects of B, it looks like you would check the 'update_fields" > kwarg for B's foreign key. > > On Monday, February 6, 2017 at 8:36:38 AM UTC-5, Oskar Persson wrote: >> >> My specific need for this at the moment

Re: Added signals that runs when adding an object to a Many-To-One relation

On Monday, February 6, 2017 at 5:59:45 AM UTC-5, Oskar Persson wrote: >> >> And we could also maybe add signals similar to pre_add and post_add that >> are sent when calling remove() and clear() on a relation set, getting a bit >> closer to QuerySet.update() >> >

Re: Added signals that runs when adding an object to a Many-To-One relation

And we could also maybe add signals similar to pre_add and post_add that are sent when calling remove() and clear() on a relation set, getting a bit closer to QuerySet.update() Den måndag 6 februari 2017 kl. 10:22:27 UTC+1 skrev Oskar Persson: > > No, if the QuerySet.update() signals were

Re: Added signals that runs when adding an object to a Many-To-One relation

init and post_init is a very expensive historical > mistake." > > [0] https://code.djangoproject.com/ticket/27809 > > On Friday, February 3, 2017 at 12:29:04 PM UTC-5, Oskar Persson wrote: >> >> It would. Though that seems like its trying to solve a bigger issue since &

Re: Added signals that runs when adding an object to a Many-To-One relation

> your use case? > > https://code.djangoproject.com/ticket/21461 > > On Friday, February 3, 2017 at 12:14:23 PM UTC-5, mtnpaul wrote: >> >> Good to know. >> >> Thanks, >> >> Paul >> >> >> On Fri, Feb 3, 2017 at 10:03 AM, Oskar Per

Re: Added signals that runs when adding an object to a Many-To-One relation

ld not require an intermediate table, so it > would be caught by pre-save and post-save on the object containing the > Foreign Key. Is that not true? > > > Paul > > On Fri, Feb 3, 2017 at 8:28 AM, Oskar Persson > wrote: > >> Hi everyone. >> >> I've creat

Added signals that runs when adding an object to a Many-To-One relation

run custom code when ever adding an object to a Many-To-One relation. There already exists a signal for Many-To-Many <https://docs.djangoproject.com/en/1.10/ref/signals/#m2m-changed> fields so why not for Many-To-One? What are your thoughts on this? Thanks Oskar Persson -- You rece