Now that we can connect to Oracle we are experiencing a new suite of problems. The stored procs we must call have data types that JS/Node.js can't handle directly. We can't ask the DB team to change the procs because this would require a cascading set of changes to C++ and Java code that is not currently under development and expects the values from these stored procs to remain constant. So far we have encountered two specific problems:
Error: CreateColumnsFromResultSet: Unhandled oracle data type: 101
It would seem this must be a problem other's have encountered. I see that you can specify the type of an OUTPARAM as in code like this:
connection.execute("call myProc(:1,:2)", ["nodejs", new oracle.OutParam(oracle.OCCISTRING)], function(err, results)
The challenge I have is that the result of the stored proc in my case is a results cursor with 58 columns of data for each result set. Of that data, most is of Oracle type "Number" with one field of type binary_double. I see in the source code where the CreateColumnsFromResultSet function is implemented and we could muck around with a copy of that function that takes an additional array of types to cast the columns too, but that seems ugly and we'd rather not modify your module if we can help it.
I'm having this problem as well, but with just running a select * from a table that it dosn't like. I'm just writing the data to file and not manipulating it at all, were would I go to just tell it to dump as a string.