I think the consensus here is to not add the extra commit, so I've
closed the ticket as wontfix.
(https://code.djangoproject.com/ticket/16735#comment:26)
Ian
On 20/08/16 15:24, Josh Smeaton wrote:
Just as an additional data point - most expressions that accept
strings internally convert them
Dear Django-Developers,
We just started using the new search ability that landed in Django 1.10
(using postgres).
Reading the documentation[1], I thought I can use `&` and `|` to join
search queries as I like[2]. This is not the case, which can easily be seen
by creating a the test-case with t
Hi Nicola,
Without a lot of familiarity of SearchQuery, in particular, it looks like a
bug to me. SearchQuery defines its own operators to work around the
limitation in Combinable, but fails to take into account that when two
SearchQuery instances are combined, you're returned a CombinedExpress
Ticket to add support for introspection of index type
- https://code.djangoproject.com/ticket/27097
On Friday, 19 August 2016 21:03:00 UTC+5:30, Tim Graham wrote:
>
> I think if we do a similar thing like we do for field introspection
> (outputting a comment like "# This field type is a guess"
Yup, that sounds like an oversight on my part. The fix would be exactly as
Josh described.
On 25 August 2016 at 13:54, Josh Smeaton wrote:
> Hi Nicola,
>
> Without a lot of familiarity of SearchQuery, in particular, it looks like
> a bug to me. SearchQuery defines its own operators to work aroun
Hi All,
While building out a vagrant image for running django's tests
(plug: https://github.com/django/django-box) I came across a problem trying
to run the javascript tests as defined by the tox.ini file. It ended up
being the same problem as raised
in https://code.djangoproject.com/ticket/25
Trey Hunner said [0], "Blanket and qunit are the only real requirements
here. We may be able to switch away from Grunt and use those together in a
more manual fashion so requirements can be upgraded easily."
[0] https://github.com/django/django/pull/4889#issuecomment-219921988
On Thursday, Augu
>From the doc: "Abstract base classes are useful when you want to put some
common information into a number of other models". In my current project I
put all common fields in abstact class, but those fields that use 'choice'
option may have different choices in different child classes.
Code Exa
