Release Notes: v0.6.6
Highlights
This release introduces advanced support for Oracle stored procedures and functions, including custom variable binding, and brings several enhancements and fixes.
🚀 Features & Enhancements
-
Custom Variable Binding for Stored Procedures and Functions
- You can now use
msg.bindVars
to manually bind input and output variables, including types and directions, for stored procedures and functions. - Example usage:
msg.query = "BEGIN :output := example_function(input_param => :input_param); END;"; msg.bindVars = { output: { dir: "BIND_OUT", type: "NUMBER" }, input_param: { dir: "BIND_IN", type: "STRING", val: input_value } };
- If
msg.bindVars
is not provided, automatic binding is performed based onmsg.payload
andmsg.query
.
- You can now use
-
Support for PL/SQL Functions & More Flexible Bindings
- Full support for calling PL/SQL functions and procedures, with flexible input/output parameter mapping.
- Improved internal transform of bind variables for advanced scenarios.
-
Result Retrieval Improvements
- More flexible result retrieval for advanced use cases.
-
Editor & Documentation Updates
- Node editor UI improved for easier query and mapping editing.
- Documentation updated for new features, including examples and usage notes.
🐛 Bug Fixes
- Port validation error handling reapplied based on user feedback.
- Miscellaneous internal fixes and code cleanups.
🛠 Dependency Updates
- Update:
oracledb
dependency upgraded to 6.3.0. - Other minor dependency bumps for improved stability.
🔗 Links
⚡️ Upgrade Notes
- No breaking changes expected. For custom PL/SQL or function use, see new
msg.bindVars
documentation and examples. - If you happen to experience issues with port validation, please verify your node configuration and update it as needed.
Thank you to all contributors and users for your feedback and support!