Re: Newer constraint declarations and Foreign Keys

2022-03-07 Thread charettes
If you're interested in following the development of the database level foreign key constraints feature you should CC to #21961 [0] The latest attempt at implementing them was recently closed due to inactivity [1] Cheers, Simon [0] https://code.djangoproject.com/ticket/21961 [1] https://github

Re: GSOC 22

2022-03-07 Thread 'Adam Johnson' via Django developers (Contributions to Django itself)
Yes - there's a wiki page here with lots of info: https://code.djangoproject.com/wiki/SummerOfCode2022 On Mon, Mar 7, 2022 at 12:31 PM Sarthak Kinge wrote: > Is django again participating in GSOC 22? > > -- > You received this message because you are subscribed to the Google Groups > "Django dev

Re: Newer constraint declarations and Foreign Keys

2022-03-07 Thread 'Adam Johnson' via Django developers (Contributions to Django itself)
No, there is not currently a way in Django to declare such constraints. You can always create them in a migration using the RawSQL operation, then rely on them in your code. This blog post relates to custom relationships which would allow you to model them, I think: https://schinckel.net/2021/07/1

Newer constraint declarations and Foreign Keys

2022-03-07 Thread dans...@gmail.com
Hi guys, I remember that there is a new way to declare constraints in class Meta on a model, and that this is preferable for unique_together constraints. I've long wanted a way with Django to have database foreign key constraints cascade in the database rather than via Django. Is there now a

GSOC 22

2022-03-07 Thread Sarthak Kinge
Is django again participating in GSOC 22? -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@go

Re: Is_ajax replacement??

2022-03-07 Thread Jet Ezra
Thanks, I think I will always add small module when needed On Thursday, February 24, 2022 at 11:33:30 AM UTC+3 Adam Johnson wrote: > The feature was deprecated in Django 3.1 - the release note covers > alternatives: https://docs.djangoproject.com/en/3.1/releases/3.1/#id2 > > If you didn't detec

Re: RFC #33561 -- Synchronize user attributes on every authentication with RemoteUserBackend

2022-03-07 Thread Adrian Torres Justo
Alright, I'm still not 100% convinced it wouldn't be best having them as separate methods, but for the sake of moving things along I'll implement it. One thing that's not quite clear: you mentioned adding a backwards compatibility warning, is this the same as a RemovedInDjangoXXWarning? Should