#30408: CheckConstraint with lookup using LIKE & % crash on PostgreSQL.
-------------------------------------+-------------------------------------
     Reporter:  David Sanders        |                    Owner:  Simon
                                     |  Charette
         Type:  Bug                  |                   Status:  assigned
    Component:  Database layer       |                  Version:  2.2
  (models, ORM)                      |
     Severity:  Release blocker      |               Resolution:
     Keywords:                       |             Triage Stage:  Accepted
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by Simon Charette):

 * status:  new => assigned
 * owner:  nobody => Simon Charette


Comment:

 FWIW it's the same class of issue as #30258 which will probably better be
 fixed by making `create_sql`/`constraint_sql` methods return `(sql,
 params)` tuples. See https://code.djangoproject.com/ticket/30258#comment:3
 and [https://github.com/django/django/compare/master...charettes
 :constraint-index-sql ungoing work to make this happen].

 I'll tentatively assign to myself to try to polish the solution suggested
 above.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/30408#comment:2>
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/066.65192972586700cf5ad30eeff2afc296%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to