Now the NAN 2 patch has landed in node-oracledb 1.4, and after a very
successful Oracle OpenWorld conference with a lot of interest in
Node.js, it's time to get back to work.
For node-oracledb 1.5 these are the things we will start to look at:
Bugs:
The aggregate row / maxRows bug (#80) and the general issue of SUCCESS_WITH_INFO handling
The autocommit issue with 11g Oracle Client (#269)
(updated) The seg fault with CALL and LOB bind (#260) This is a DB issue. You can use BEGIN/END as a work around, or ask for an Oracle patch from Oracle Support for bug 21560713.
The interupt handling issue (#128) Will have to defer this again :(
Any other crashes that are reproducible.
(updated) RS memory leak (#307) Thought we had this identified, but it was not to be.
No promises that these will get resolved, but they are up there on the list.
Ongoing investigation (has no ETA):
What is involved in delivering precompiled binaries (#18)
LOB API "simplification". Also looking at preventing incorrect
sequences of underlying LOB calls causing problems.
I'll update this issue if there are any changes to the plan.
Now the NAN 2 patch has landed in node-oracledb 1.4, and after a very successful Oracle OpenWorld conference with a lot of interest in Node.js, it's time to get back to work.
For node-oracledb 1.5 these are the things we will start to look at:
Bugs:
The seg fault with CALL and LOB bind (#260)This is a DB issue. You can use BEGIN/END as a work around, or ask for an Oracle patch from Oracle Support for bug 21560713.The interupt handling issue (#128)Will have to defer this again :(RS memory leak (#307)Thought we had this identified, but it was not to be.No promises that these will get resolved, but they are up there on the list.
Ongoing investigation (has no ETA):
I'll update this issue if there are any changes to the plan.