v2.19.0-beta.1

Changelog

Bug fixes and improvements

Server

• Fix nullable field omitted from action response if not present in the webhook response.
• Log cron triggers fetched for event generation within 10-minute timeframe under cron-event-generator-process log type.
• Make pg_run_sql as an alias of run_sql
• Fix suggestion issue with the *_suggest_relationships metadata API.
• Add a content-length response header to all endpoints
• Improve phrasing for the "conflicting type definitions" error message
• Add a new option to set_query_tags API to omit the request_id field from Query Tags. Recommended when Query Tags are used in conjunction with Prepared Statements. (Cloud / Enterprise Edition only)

Console

• Add suggested relationships (foreign keys based) to the new table relationships page
• Allow creating remote joins from and to the same remote schema
• Fix the export data dropdown menu visibility on browse rows page
• Fix suggested relationship name creation
• Add streamlined UX for creating and maintaining database relationships. This feature can be enabled by a feature flag in the settings menu.
• Fix the issue with the edit connection form for GDC sources not populated with the saved values.
• Fix edit row when the column is "generated always" (fix #9389)

Data Connectors

• Add check to verify that source in header and jdbc_url line up with the request path. (Cloud / Enterprise Edition only)
• Bugfix for failure of the super-connector to properly order results based on a single column aggregate. (Cloud / Enterprise Edition only)
• Single column aggregates in query API requests now include the scalar type of the result of the aggregation function