v0.7.4

v0.7.4 - Major Usability, Stability, and Upgrade Fixes

This is a significant stability and usability release that addresses several important bugs and dramatically improves the user experience. Upgrading is highly recommended for all users.

✨ New Features & Major Improvements

• Smart Named Binding (A More Intuitive Node!): You can now send a msg.payload object directly to an INSERT or UPDATE query that uses named binds (e.g., VALUES (:name, :email)). The node is now smart enough to automatically ignore any extra properties in your payload (like fax, id, etc.) that aren't in your query. This completely solves the common ORA-01036: illegal variable name/number error and makes the node work exactly as you'd expect.

• Intelligent Node Status: The node's status display is now much more helpful:

  • Shows a blue "running..." status the moment a query starts.
  • If a query fails (e.g., due to bad SQL syntax), the status will now show the error and stay red, so you know exactly what went wrong.
  • The status only returns to a green "connected" after a successful query.

🐛 Bug Fixes

• Fixed Invalid Server Configuration on Upgrade: This release permanently fixes the bug where existing oracle-server nodes would show a red triangle and an "invalid properties" error after upgrading from versions prior to 0.7.0. The upgrade path is now seamless.

• Fixed "type_already_registered" Startup Error: A bug in the build process that caused Node-RED to sometimes crash or throw warnings on startup has been completely resolved by overhauling the build scripts.

This release combines the work intended for several patch versions into one robust update. Thank you to the community for the detailed bug reports that made these improvements possible!

v0.7.3

v0.7.3 Fix node type already registered warning in palette and logs.

Full Changelog: 0.7.2...v0.7.3

0.7.2

Upgrade fix to address invalid node config error.

Full Changelog: v0.7.1...0.7.2

v0.7.1

Fixed: Corrected an upgrade issue where existing server configurations would be marked as invalid after updating to 0.7.0.

Full Changelog: v0.7.0...v0.7.1

v0.7.0

Refactor Oracle DB Node and Server Implementation

• Updated variable declarations to use const and let for better scoping.
• Enhanced validation for port, poolmin, poolmax, and pooltimeout properties in the oracle-server node.
• Improved the oneditprepare function for better readability and maintainability.
• Added new options for sending single messages with metadata in the oracledb HTML.
• Updated documentation for the oracledb node to clarify input and output expectations.
• Introduced TypeScript configuration files for both HTML and Node.js directories.
• Rewrote the Oracle DB node to utilize connection pooling for improved performance.
• Removed deprecated TSLint configuration in favor of TypeScript's built-in checks.
• Cleaned up legacy files and configurations, including tsd.json and the root tsconfig.json.

v0.6.6

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 on msg.payload and msg.query.

• 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

• Full commit history and changes
• README and usage documentation

---

⚡️ 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!

0.6.5

What's Changed

• Update readme.md by @vtulluru in #47
• Bump oracledb from 6.0.3 to 6.3.0 by @dependabot in #43
• Update oracledb.html by @vtulluru to reapply port validation fix in #46

Full Changelog: v0.6.4...v0.6.5

v0.6.4

What's Changed

• Bump @types/jquery from 3.5.14 to 3.5.16 by @dependabot in #23
• Trigger the catch node on error by @JheSue in #33
• Ensure port validation returns boolean by @knolleary in #37
• Bump oracledb from 5.5.0 to 6.0.3 by @dependabot in #31

New Contributors

• @JheSue made their first contribution in #33
• @knolleary made their first contribution in #37

Full Changelog: v0.6.3...v0.6.4

v0.6.3

1. Fix node connection issues with DPI-1010 and DPI-1080
2. dependency updates
   • Bump del from 6.1.1 to 7.0.0
   • Bump chai from 4.3.6 to 4.3.7
   • Bump @types/mocha from 9.1.1 to 10.0.1
   • Bump decode-uri-component from 0.2.0 to 0.2.2
   • Bump oracledb from 5.4.0 to 5.5.0

v0.6.2

Dependency updates

oracledb ^5.1.0 → ^5.4.0
@types/jquery ^3.5.5 → ^3.5.14
chai ^4.2.0 → ^4.3.6
merge2 ^1.3.0 → ^1.4.1
source-map-support ^0.5.19 → ^0.5.21