xt? I don't expect this to be anywhere near
the best solution, but I think it's an idea that's worth some
consideration. Should I - for example - create a pull request?
Regards,
Nigel
On Tuesday, 27 April 2021 at 18:56:34 UTC+1 NPB wrote:
> Hi there -
>
> Should I cr
Hi there -
Should I create a ticket?
Thanks and regards,
Nigel.
On Wednesday, 14 April 2021 at 16:19:54 UTC+1 NPB wrote:
> Hi -
>
> Here is something I tried out:
>
> https://github.com/nigelbayliss/django
>
> I am no Python expert, and having never done this before I'
e existing *unify by values *solution.
Regards,
Nigel
On Tuesday, 13 April 2021 at 14:23:15 UTC+1 NPB wrote:
> P.S.
>
> I think I will have a stab at creating a solution. I'll run it through the
> queries, aggregation, and aggregation_regress tests.
>
> Thanks,
> Nigel
>
P.S.
I think I will have a stab at creating a solution. I'll run it through the
queries, aggregation, and aggregation_regress tests.
Thanks,
Nigel
On Tuesday, 13 April 2021 at 13:34:30 UTC+1 NPB wrote:
> Hi Mariusz and Simon,
>
> Yes, agreed, it is true that Oracle doesn&#x
Hi Mariusz and Simon,
Yes, agreed, it is true that Oracle doesn't support column aliases in GROUP
BY. It is possible to use "GROUP BY ", but only if a
specific Oracle session parameter setting is used. IMO it would be
undesirable to make this setting mandatory for Django, though.
Oracle defini
the aggregation issue[1] if you'd like to change
> this behaviour.
>
> Cheers,
> Simon
>
> [0]
> https://github.com/django/django/commit/6dbe56ed7855f34585884a2381fb1cec22ddc824
> [1] https://code.djangoproject.com/ticket/27632
>
> Le samedi 3 avril 2021 à 18:30:
Hi,
Can you tell me why *execute* in .../backends/oracle/base.py sets
*unify_by_values=True* when it calls *_fix_for_params*? It has an
interesting effect on the Oracle cursor cache.
For example, if I use a Django model called Logger like this:
from . import models
...
a = models.Logger(t1=
