Context Navigation

Changes between Initial Version and Version 1 of Ticket #35836, comment 2

initial	v1
1	1	Django 3.2 has been EOL for 6 months now and while we accept patch to allow extension of the ORM we don't offer any guarantees towards backward compatibility around `sql.Query` API changes.
2	2
3		In other words, if you extend undocumented and unstable part of the framework you must be prepared to adapt your code and provide a solution that goes beyond bisecting the origin of ~~your breakage~~.
	3	In other words, if you extend undocumented and unstable part of the framework you must be prepared to adapt your code and provide a solution that goes beyond bisecting the origin of the problem you are experiencing.
4	4
5	5	In the case of 14c8504a37afad96ab93cf82f47b13bcc4d00621 I think it's a sane change in towards extensibility and something we'd want to keep in `main`. `SQLQuery.get_compiler` is by no means meant to be used as a hook to augment the where clause of a `QuerySet`, this should be done at the manager level.