#28859: Django hides NO_DATA_FOUND exception from database with Oracle backend.
-------------------------------------+-------------------------------------
     Reporter:  Jani Tiainen         |                    Owner:  felixxm
         Type:  Bug                  |                   Status:  assigned
    Component:  Database layer       |                  Version:  2.0
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:
     Keywords:  oracle               |             Triage Stage:  Accepted
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by felixxm):

 Replying to [comment:4 Jani Tiainen]:

 `INSERT` without `RETURNING` clause raises `NO_DATA_FOUND` exception also
 with a wrapped connection in Django, but when we add `RETURNING` clause,
 both a `cx_Oracle` plain connection and a wrapped connection in Django
 doesn't work properly, e.g.:

 {{{
 >>> cursor.execute('''
     INSERT INTO "BACKENDS_SQUARE"("ROOT", "SQUARE")
     VALUES(2,4) RETURNING "BACKENDS_SQUARE"."ID" INTO :v_id
 ''', {'v_id': v_id})
 }}}

 I raised the issue on `cx_Oracle` https://github.com/oracle/python-
 cx_Oracle/issues/131.

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

Reply via email to