necessary group by, or if this simply a bug
El miércoles, 6 de diciembre de 2017, 10:28:22 (UTC-3), Cristiano Coelho
escribió:
>
> After testing for a while, there really doesn't seem to be a good way to
> do this. .
>
> Annotation is required since the query is filter
that ends up almost adding 3 times more
database query time do to the horrid count query generated.
El viernes, 24 de noviembre de 2017, 18:04:21 (UTC-3), Cristiano Coelho
escribió:
>
> Hello Simon,
>
> You are right, the score is really not meant to be attached so a custom
&g
gt; way easier and provide help for users in the situation as you.
>
> Best,
> Simon
>
> Le vendredi 24 novembre 2017 08:14:10 UTC-5, Cristiano Coelho a écrit :
>>
>> Hello Simon,
>>
>> That private API is good to know, but now that I think of it would still
>
n you are
>>> performing your `count()` because some annotations could interfere with
>>> grouping
>>> somehow.
>>>
>>> There is an open ticket[0] to add support for an `alias()` method that
>>> would
>>> allow the ORM to clear/ignore
that
> would
> allow the ORM to clear/ignore the specified expressions if it's not
> referenced
> in the query.
>
> In the mean time I think the best approach would be to avoid annotating the
> queryset if your don't need to reference the score.
>
> Cheers
Hmm, should I try with the dev mailing list? Guess it's something no one
faced before?
El martes, 14 de noviembre de 2017, 22:54:23 (UTC-3), Cristiano Coelho
escribió:
>
> I'm getting some very odd query when combining annotate with count. See
> the f
I'm getting some very odd query when combining annotate with count. See the
following:
>>> q =
> Vulnerability.objects.annotate(score=WordTrigramCustomSimilarity('test','summary'))
> >>> q.count()
> 3094
> >>> print connection.queries[-1]
> 'SELECT COUNT(*)
> FROM (
> SELECT "vulnerabilitie
ls release, but it's going
> to take a little time.
>
> Andrew
>
> On Mon, Aug 7, 2017 at 4:21 AM, Cristiano Coelho > wrote:
>
>> About docs here: http://channels.readthedocs.io/en/stable/deploying.html
>>
>> "The fundamental difference is that th
For some reason my original question got lost.
http://channels.readthedocs.io/en/stable/deploying.html
I don't quite understand this part:
The fundamental difference is that the group mechanic requires all servers
serving the same site to be able to see each other; *if you separate the
site u
About docs here: http://channels.readthedocs.io/en/stable/deploying.html
"The fundamental difference is that the group mechanic requires all servers
serving the same site to be able to see each other*; if you separate the
site up and run it in a few, large clusters, messages to groups will only
10 matches
Mail list logo
