#34963: Recursive and other "combinator" queries broken in django-cte
-------------------------------+--------------------------------------
Reporter: Daniel Miller | Owner: nobody
Type: Bug | Status: closed
Component: Uncategorized | Version: 4.2
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by Simon Charette):
Hello Daniel!
I sympathize with the desire to avoid duplicating large chunks of code in
django-cte and I appreciate that you maintain such a solution but asking
for the development team to maintain compatibility with its internal
interface when adjusting bugs of the interface it maintains is not
sustainable particularly for regressions in versions that have been
released for a few months already. When making these changes we try to
think of ways that are not too invasive but there's only so much we can do
to account for all cases.
I'm very much open to reviewing patches that would reduce the maintenance
burden that you face (is there a kwarg that can be passed? a different
function breakdown be used?) in `main` or that implements smarter way of
doing things that avoids unnecessary aliasing such as proper `ORDER BY
$index` support but stability of the ORM internals cannot be guaranteed by
team in its current state.
> Is there a way to implement a fix so that it only affects queries where
aliases are needed?
I believe that if you build and maintain a package that relies on the
stability of ORM internals you must be prepared to deal with regressions
against `main` and suggest alternative solutions when they happen. I'm
afraid the ship has already sailed for the 4.2 backport support window and
I'm not even sure it would qualify given the internal nature of SQL
compilation.
--
Ticket URL: <https://code.djangoproject.com/ticket/34963#comment:5>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018bc5244ed3-d2c062cd-8aa7-4960-b54e-0e4a4e8d11d6-000000%40eu-central-1.amazonses.com.
