Re: Allow turning off fuzzy matching for makemessages (Reopen #10852)

As you can see in the ticket you mention (see last comment), it is already possible to do so by adding a custom version of the makemessages command in your project. Hope this helps, Claude -- You received this message because you are subscribed to the Google Groups "Django developers (Contr

Re: "Unify by values" setting in Oracle's base.py

Hi Nigel, Creating a subquery only looks like a good solution for a limited number of cases. As far as I'm aware it will also change an execution plan and can cause a performance regression in complicated queries. We also cannot group by column aliases on Oracle as proposed in PR14251

Allow turning off fuzzy matching for makemessages (Reopen #10852)

Fuzzy matching is not useful for me and confuses my translators. I would like to be able to pass an option to makemessages that passes the --no-fuzzy-matching option to msgmerge to turn it off. I understand it is useful for some people, so fuzzy matching should remain the default. I propose all

Re: "Unify by values" setting in Oracle's base.py

Hello Nigel, > I wonder if it would be possible to catch cases where a bind variable would normally be included in both the SELECT list and the GROUP BY. It should be possible at the compiler level which is overriddable by backend (e.g. here's how it's done for a different purpose on MySQL back

Re: "Unify by values" setting in Oracle's base.py

Hi Simon, Thanks for tracking that down. I see - an interesting problem that lacks an obvious solution. Nevertheless, there is a generic way to deal with this and it will optimize OK in Oracle (at least in the vast majority of cases). select x, sum(sal) from (select :arg0 * deptno as x, sal f