#30484: Using RawSQL with CheckConstraint
-------------------------------------+-------------------------------------
     Reporter:  David Sanders        |                    Owner:  nobody
         Type:  New feature          |                   Status:  closed
    Component:  Database layer       |                  Version:  2.2
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:  wontfix
     Keywords:                       |             Triage Stage:
                                     |  Unreviewed
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by Gavin Wahl):

 The other ticket is fixed, but it is still not possible to use expressions
 in check constraints. The proposed workaround with lookups doesn't work
 because my check constraint uses a function that takes multiple arguments
 (I need to be able to do `CHECK num_nonnulls(a, b, c) = 1`).

-- 
Ticket URL: <https://code.djangoproject.com/ticket/30484#comment:3>
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.2ced66dd633f5a00cf85f92eb52bb9eb%40djangoproject.com.

Reply via email to