Re: Transaction APIs do not consult the DB router to choose DB connection

> On 2 Jun 2021, at 07:49, N Aditya wrote: > > Below are a few things I'd like to clarify: > Are you referring to thread-locals as `global state/variables` in your > previous message ? Yes. > If so, why suggest something which you consider bad practise ? You rejected the good practice before —

Re: `Model.validate_unique` excluding partial unique constraint

Thanks for the thorough answer. I also realize now that it worked in my app only because of another side effect when my instance was saved.. I started to take a look at the ORM part where the check method should be implemented as I'm not used to it. Shouldn't .check() be implemented on Q and

Re: Transaction APIs do not consult the DB router to choose DB connection

Hi Aditya, I think the basic issue is that the DB Routers framework is not the right tool for the task you have in mind. You are trying to redirect all database activity according to request parameters. The routers are built for specific uses, and -- by design -- they don't cover all cases; it's

Django security releases issued: 3.2.4, 3.1.12, and 2.2.24

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2021/jun/02/security-releases/ -- You received this message because you are subscribed to the Google Groups "Django developers