#29644: String representation of SearchQuery gives inaccurate results -------------------------------------+------------------------------------- Reporter: Alex Krupp | Owner: Tom | Forbes Type: Bug | Status: closed Component: contrib.postgres | Version: 2.0 Severity: Normal | Resolution: fixed Keywords: SearchQuery search | Triage Stage: Ready for | checkin Has patch: 1 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 -------------------------------------+------------------------------------- Changes (by Tim Graham <timograham@…>):
* status: assigned => closed * resolution: => fixed Comment: In [changeset:"a3df7574f934673d9c77154bb3e69917ebf85e3e" a3df757]: {{{ #!CommitTicketReference repository="" revision="a3df7574f934673d9c77154bb3e69917ebf85e3e" Fixed #29644 -- Made SearchQuery.__str__() reflect negation and grouping. }}} -- Ticket URL: <https://code.djangoproject.com/ticket/29644#comment:7> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the Google Groups "Django updates" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-updates+unsubscr...@googlegroups.com. To post to this group, send email to django-updates@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/066.8e10b39769b5be2e2c41c8aa08eb95d5%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.