Alexandru Mărășteanu
Alexandru Mărășteanu
I'm aware https://github.com/arneb/django-generic-confirmation/pull/5 exists, but that sets it to `SET_NULL` instead of the `CASCADE` specified in https://github.com/arneb/django-generic-confirmation/commit/0f8cf5865307e4d123107131b01593123c400cb7
Oh, I see. I wasn't expecting it to deal with partitions as that would be difficult. I was, however, expecting it to delete the triggers and stuff. Would that be...
`ForeignKey`s should work fine. I didn't check with `ManyToManyField`s and `OneToOneField`s though.
I understand your pain. I built this in a couple of hours one day when I needed to rename a couple of models. Given this stuff is barely documented (I...
I'm not sure I understand. Could you please provide more info?
I see. No, it doesn't. Should it?
Thanks for the link. I read that article before implementing this. It doesn't account for other DB engines. For example, SQLite stores sequence information inside a `sqlite_sequence` table and `ALTER...
Ideally renaming a sequence would be implemented as a db operation. Those, however, are not documented and currently I'm not sure how to do that.
One way to implement an operation would be to simply inherit either `RunPython` or `RunSQL` and run the appropriate query (or do nothing?) depending on the engine.
Note I was able to run the tests in my account but they fail: https://github.com/alexei/django/actions/workflows/tests.yml