Re: bug involving multiple IN/OUT parameters
Michael Bayer <[email protected]>
| Newsgroups | gmane.comp.python.db.cx-oracle |
|---|---|
| Message-ID | <[email protected]> |
On Aug 28, 2013, at 6:19 AM, Amaury Forgeot d'Arc <[email protected]> wrote: > > 2013/8/28 Michael Bayer <[email protected]> > # 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. ------------------------------------------------------------------------------ Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk _______________________________________________ cx-oracle-users mailing list cx-oracle-users-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org https://lists.sourceforge.net/lists/listinfo/cx-oracle-users
signature.asc
(application/pgp-signature, 495 B)
-----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iQEcBAEBAgAGBQJSHiY2AAoJEDMCOcHE2v7hcYEIAJkVFdXTJ1WUbpkb/kcVbEli CpV/sDEUaTIlZdn5PSYnfUmWRfWSC8PxRfZHnp+fqenu40yo7o+58oTMvW9s42K1 CcOz3TiRzmuIIS/mcvDX7O14q8lh80ClgrWKZxlQqFXKSdqorm1lxA3v2WAVhDms w2yuYOM2I8Ea6Tz+QFblQVlvqspp8FeOEQDbM9yEcMZlJRkrPixMsY4YYmsejuxT XAxAdeCFAMINe/Yy9XKdGKaLxDkv2cXPs71BuxsuypKHXjgcG2TNfsRIyEhaubi5 z25Vo0aVi3NpeZBSd2sDitB6Lmo8rpG+R1Ge1Occ9jO9MTg722/cQ05kRExXJRQ= =0o0B -----END PGP SIGNATURE-----