Editor completion is only useful when it knows the whole schema an engineer can reach, not just the part described in the metadata dictionary. This release widens the reach of schema-aware completion in two directions: to tables the dictionary does not describe, and across every database the user can access.
Columns and foreign keys beyond the dictionary
- JDBC-metadata path. For a table that is not held in the metadata dictionary, completion now reads the engine's own catalogue over JDBC to offer its columns.
- Foreign keys included. The same path resolves the table's foreign keys, so a join target is suggested from the live relationship rather than left blank.
Cross-database code resolution
- Every accessible database at once. Completion for server-side JavaScript modules and functions queries the dictionary code across all databases the user can access concurrently, rather than one database at a time.
- Engine-aware handling. The lookups account for the specific engine behind each database, so results stay correct across a mixed estate.
The result is completion that reflects the schema and code actually in front of the engineer, whether or not a table is registered in the dictionary and regardless of which accessible database holds it.