#22489: Missing as_sql() implementation for __search lookup
-------------------------------------+-------------------------------------
     Reporter:  jakub                |                    Owner:  nobody
         Type:  Bug                  |                   Status:  closed
    Component:  Database layer       |                  Version:  master
  (models, ORM)                      |               Resolution:  fixed
     Severity:  Normal               |             Triage Stage:  Accepted
     Keywords:  mysql, search,       |      Needs documentation:  0
  full-text, __search, lookup        |  Patch needs improvement:  0
    Has patch:  1                    |                    UI/UX:  0
  Needs tests:  1                    |
Easy pickings:  0                    |
-------------------------------------+-------------------------------------

Comment (by Anssi Kääriäinen <akaariai@…>):

 In [changeset:"4b6ba2c1d1dcf6d7d587ee19b3565879ab8ee219"]:
 {{{
 #!CommitTicketReference repository=""
 revision="4b6ba2c1d1dcf6d7d587ee19b3565879ab8ee219"
 [1.7.x] Fixed #22489 -- missing implemenation for search lookup

 When custom lookups were added, converting the search lookup to use
 the new Lookup infrastructure wasn't done.

 Some changes were needed to the added test, main change done by
 committer was ensuring the test works on MySQL versions prior to 5.6.

 Backport of 7131e14d00 from master
 }}}

-- 
Ticket URL: <https://code.djangoproject.com/ticket/22489#comment:5>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.7cbcc7a5729cef7471569a90204f237b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to