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 anINSERT
orUPDATE
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 (likefax
,id
, etc.) that aren't in your query. This completely solves the commonORA-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!