DBeaver Auto complete for Azure Synapse Serverless

[DantasB]

Azure Synapse Serverless has only External Tables and Views.

The auto complete for these External tables only works if we use the full qualified name for the table "database_name.schema.table_name" which is different from the SQLServer (for example) "table_name".

Example of auto complete working for Synapse Serverless:

Example of auto completeworking for SQLServer:

Is there any place where i can configure to use just the table_name, instead of the full qualified name to use the autocomplete easier?

Thx!

[ged-yuko]

Table name here can appear in two positions:

• as a table reference in the FROM clause;
• as part of the qualified column name in the column-list of SELECT clause (SELECT table.column FROM table).

You screenshot shows column completion list. It just uses already existing table reference obtained from the FROM clause.

For table reference completion list (in the FROM clause) it uses current active object, which you can select in the main toolbar when the input focus belongs to the SQL Script editor:

For example here is a public schema of the dvdrental database selected. Tables belongig this selected schema will be proposed in form of tableName. Tables belonging any other schema will be proposed in form of schemaName.tableName.

If your question is about how completion proposes table reference - the answer is: you should change the current schema with toolbar selector.
If your question is about how completion proposes qualified colum names - there is an option to force column qualified names (see Qualified column names checkbox at Editors -> SQL Editor -> Code Completion preference page), but no option to modify format of this name. By default DBeaver proposes qualified column names only if table alias is presented or there is a column name ambiguity between different tables.

Basically you can just specify table alias in FROM clause, then qualified column name proposals will have this alias instead of the table name:
SELECT t.column from schema.table t

If you are interested in another setting to change how qualified column names are proposed, you can create a feature request.