django http://cgit.adnoto.dev/django.git/atom?h=main 2026-04-30T23:52:11Z 2026-04-30T23:52:11Z Raoni Timo raoni@relume.io 2026-04-30T13:57:27Z urn:sha1:9f790ef1a0f356cf6342b5d57bbaeac35aed0d9f Setting "check" in OPTIONS["pool"] previously raised TypeError because the PostgreSQL backend always passed check= to ConnectionPool() and unpacked **pool_options on top, regardless of CONN_HEALTH_CHECKS. The user's callable now takes precedence via setdefault(); pool_options is copied first to avoid mutating the user's settings dict. 2026-04-18T06:53:21Z Mariusz Felisiak felisiak.mariusz@gmail.com 2026-04-18T06:53:21Z urn:sha1:ed79c5959add54b6e8ea589ec601e0d2e801517e 2026-04-16T09:28:19Z Tim Graham timograham@gmail.com 2026-04-16T09:28:19Z urn:sha1:82a2465f71a1f5cbfe3811952c0d07482dea71c6 2026-03-20T20:31:25Z Aarni Koskela akx@iki.fi 2026-03-14T23:04:26Z urn:sha1:994fa7780d73f6d618dc3a03339e96b5353b4e71 Based on Daniele Varrazzo's comment in https://github.com/psycopg/psycopg/issues/1273#issuecomment-3986829769 2026-03-19T16:24:17Z Simon Charette charette.s@gmail.com 2026-02-01T22:02:49Z urn:sha1:5146449a38222dc74f8f1ba88a7a7ef681e93101 Now that user provided aliases are systematically quoted there is no need to disallow the usage of the dollar sign on Postgres. 2026-03-19T16:24:17Z Simon Charette charette.s@gmail.com 2026-02-01T21:53:54Z urn:sha1:f05fac88c4699c6d04a8f1ac3328cf6c7bd39228 This ensures all database identifiers are quoted independently of their orign and most importantly that user provided aliases through annotate() and alias() which paves the way for dropping the allow list of characters such aliases can contain. This will require adjustments to raw SQL interfaces such as RawSQL that might make reference to ORM managed annotations as these will now be quoted. The `SQLCompiler.quote_name_unless_alias` method is kept for now as an alias for the newly introduced `.quote_name` method but will be duly deprecated in a follow up commit. 2026-03-13T00:01:02Z Simon Charette charette.s@gmail.com 2025-11-22T18:32:34Z urn:sha1:1a8fd5cf75bf855852f6bc2f75c3da9f7b145669 The lack of ability of the get_placeholder call chain to return SQL and parameters separated so they can be mogrified by the backend at execution time forced implementations to dangerously interpolate potentially user controlled values. The get_placeholder_sql name was chosen due to its proximity to the previous method, but other options such as Field.as_sql were considered but ultimately rejected due to its different input signature compared to Expression.as_sql that might have lead to confusion. There is a lot of overlap between what Field.get_db_prep_value and get_placeholder_sql do but folding the latter in the former would require changing its return signature to return expression which is a way more invasive change than what is proposed here. Given we always call get_db_prep_value it might still be an avenue worth exploring in the future to offer a publicly documented interface to allow field to take an active part in the compilation chain. Thanks Jacob for the review. 2026-03-08T11:08:27Z Tim Graham timograham@gmail.com 2026-03-08T11:08:27Z urn:sha1:787166fe27b0e7c7f97505da5766cfa72e76ae25 It's useful on MongoDB. 2026-02-28T15:01:08Z Tim Graham timograham@gmail.com 2026-02-17T02:27:35Z urn:sha1:202eca7795710c82cd64a248650afc64f905a17e Needed on MongoDB. 2026-02-27T22:12:07Z S​age Abdullah me@laymonage.com 2026-02-27T22:12:07Z urn:sha1:b415cef5d21cd5beac212a833f9f0b7727899f64 The "spawn" and "forkserver" multiprocessing modes were affected.