Re: [cx-oracle-users] bug involving multiple IN/OUT parameters

[Michael B. <mi...@zz...>]

On Aug 28, 2013, at 6:19 AM, Amaury Forgeot d'Arc <ama...@gm...> wrote:

> 
> 2013/8/28 Michael Bayer <mi...@zz...>
> # z=IN, x=OUT, y=OUT, breaks every time in this case:
> # ORA-24369 required callbacks
> # not registered for one or more bind handles
> # different combinations work/fail somewhat randomly, though deterministically
> # for a given combination.
> cursor.execute(
>         "INSERT INTO t1 (y, z) VALUES (1, :z) RETURNING t1.x, t1.y INTO :x, :y",
>         {"z": 1, "x": x, "y": y})
> 
> According to documentation, it's even surprising that it works sometimes:
> http://docs.oracle.com/cd/B10501_01/appdev.920/a96584/oci05bnd.htm#420693
> """
> Even if the application can be sure that it will only get a single value back in the RETURNING clause, it must still bind in OCI_DATA_AT_EXEC mode and use callbacks
> """
> 
> cx_Oracle has no support at all for this OCI_DATA_AT_EXEC.

thanks for your reply.  So it seems like it is possible, but OCI requires some extra API calls.    Does cx_Oracle have any kind of issue tracker in use?    At least the task could be logged as a potential enhancement, and something to point my users towards when their Oracle RETURNING clauses fail.