'DML RETURNING' aka RETURNING INTO clause does not bind with OUT parameter about node-oracledb HOT 13 CLOSED

Thanks for reporting this. It's a known issue on our list; your report helps prioritize it.

from node-oracledb.

+1

from node-oracledb.

I think this is needed for us to be able to use this repo.

from node-oracledb.

(we're returning a single value by the way)

from node-oracledb.

This feature is required to switch to this project. And the example above is exactly what we are doing.

from node-oracledb.

I'm sitting in a meeting right now discussing edge cases and how to make them easy to use.

from node-oracledb.

Any update on this issue? What was the outcome from the meeting? Thanks!

from node-oracledb.

@jamhall the feature is being worked on.

from node-oracledb.

Excellent. Thanks for your reply.

from node-oracledb.

hi @cjbj, any ETAs on this feature?

Thanks!

from node-oracledb.

@aberigle I don't do ETAs, but I will say we had a long meeting last night to triple-check we have the best design for RETURNING INTO binds with (future) PL/SQL IN/OUT array binds and normal IN array insert binds and any future OCI plans. A SQL RETURNING INTO clause can return an array, but we think most people will only be returning a single value. The outcome (and here's the timing hint) was that the code we currently have is not planned to change: a RETURNING INTO bind will always return an array, containing zero or more elements depending what was matched by the DML statement. Only string & number datatypes will be supported at first.

from node-oracledb.

@cjbj thanks for the input!

I'll be keeping an eye on this issue

from node-oracledb.

@aberigle That's definitely the last time I give a release date hint. But now we something to play with. Yay. Check my comments in https://blogs.oracle.com/opal/entry/node_oracledb_0_5_0

Note RETURNING INTO bind variables are always returned as arrays of zero or more elements.

from node-oracledb.