#34858: Output field for combined PositiveIntegerField is not properly resolved.
     Reporter:  Toan Vuong           |                    Owner:  Toan
                                     |  Vuong
         Type:  Bug                  |                   Status:  closed
    Component:  Database layer       |                  Version:  4.2
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:  fixed
     Keywords:                       |             Triage Stage:  Ready for
                                     |  checkin
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0

Comment (by Toan Vuong):

 > Coalesce() on Oracle ‚Äčexplicitly checks the output_field when it's
 compiled (for Cast.default), on other database the output_field is not
 used when Coalesce() is compiled so it doesn't crash. The crash on Oracle
 is a side-effect of the current implementation, IMO, there is no need to
 change it.

 Thanks, this is what I was missing. In our local copy of Django I
 essentially added a try/catch on that `as_oracle` function which worked,
 but I didn't realize that was only called in some cases but not others.

Ticket URL: <https://code.djangoproject.com/ticket/34858#comment:11>
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 view this discussion on the web visit 

Reply via email to