The 7.9.4 beta 1 is up as of today. The focus of this release is security, and one of the new features that can affect module developers is named queries.
Named queries are a way to define database queries in advance, so that clients can’t run random queries. An added benefit is that queries become easy to reuse throughout your project.
As a module developer, here’s what you need to know about named queries:
- Clients may or may not have legacy db access enabled. If they don’t, the client is restricted to only using named queries. Your module needs to handle this gracefully. (If legacy db access is disabled, things like tag history, transaction groups and alarm history will still work, because those queries are predefined.)
- The API for report datasources has changed slightly. If you have written a custom datasource in your module, you can probably use null for the new argument.
- If your module has a panel for authoring db queries, similar to the component binding panel in Vision, you will need to also accommodate named queries.