Re: GSOC 2023 Discussion and Feedback: Database-level Cascades

> > Thank you for your suggestion and nice implementation example. I would try > to include that approach too. > No, that was just an example of a workaround without any of the benefits of Django's emulation – the presence of a workaround often goes into determining whether it's worth working on a

Re: GSOC 2023 Discussion and Feedback: Database-level Cascades

Hi David, Thank you for your suggestion and nice implementation example. I would try to include that approach too. *Regards,* Akash Kumar Sen LinkedIn | GitHub On Thursday, March 30, 2023 at 5:00:10 A

Re: GSOC 2023 Discussion and Feedback: Database-level Cascades

The difficulty of switching to database level constraint effectively resides in how your lose the great parts of cascade deletion emulations most notably signals post and pre-delete signals. If you're willing to make this compromise then you must make sure that all cycle of model relationships

Re: GSOC 2023 Discussion and Feedback: Database-level Cascades

Hey David. Nice example! I've done this, again just PostgreSQL, overriding the schema editor's sql_create_fk and sql_create_column_inline_fk to add to the necessary ON DELETE (for an FK subclass), but doing it with a constraint is a lovely touch. (I shall play with that 😜) I didn't look at

Re: GSOC 2023 Discussion and Feedback: Database-level Cascades

Hi Akash, Database-level cascading deletes is a topic that has been discussed often since, well probably the dawn of Django 😁 From recollection the main issue isn't the implementation, it's getting it to play nicely with Django's cascading emulation. There are other tickets, but I believe this i