Option to disable all metadata queries

[emanueol]

---

--TEST 1: when executing SQL queries in Snowflake, I see 2 extra queries done by dbeaver on same session:

--I found 2 settings to turn off suggested in:

preferences > editors > data editor >
[ ] Read table metadata (unique keys)
[ ] Read table references (foreign keys)

But that only removes one of the rogue metadata queries from being executed:

---

--TEST 2 - another test, simple disconnect/connect and execute 3 USE + query to grab all queries executed

I executed 4 queries but Snowflake says DBEaver executed 11 queries in total:
my 4 queries:
use role sysadmin; use database db; use schema s;

the 7 extra metadata queries that seems DBeaver enjoying doing on its own :(
`
--1st dbeaver query:
SELECT DISTINCT
CASE TABLE_TYPE
WHEN 'BASE TABLE' THEN 'TABLE' // For backward compatibility.
ELSE TABLE_TYPE
END AS TABLE_TYPE
FROM INFORMATION_SCHEMA.TABLES;

--2nd dbeaver query:
SELECT CURRENT_DATABASE(), CURRENT_SCHEMA();

--3rd dbeaver query:
SELECT CURRENT_DATABASE(), CURRENT_SCHEMA();

--4th dbeaver query:
show /* JDBC:DatabaseMetaData.getCatalogs() */ databases in account

--5th dbeaver query:
show /* JDBC:DatabaseMetaData.getSchemas() */ schemas in database "DB"

--6th dbeaver query:
USE DATABASE DB;

--7th dbeaver query:
SELECT CURRENT_DATABASE(), CURRENT_SCHEMA();
`

Is there any options to disable/prevent DBEAVER from executing ANY queries on its own ?
If I execute 4 queries, I only want to see 4 queries executed in snowflake.

Thanks ~

[LonwoLonwo]

Hello @emanueol

DBeaver uses this query to identify your current schema/database in the SQL Editor.

SELECT CURRENT_DATABASE(), CURRENT_SCHEMA();

Also, we now have a new idea.
We can add a new setting on the Preferences -> Connections -> Metadata page.
Something like "Disable extra metadata reading".

This setting will disable all extra metadata queries. All metadata synchronization.
Only direct requests will work (like navigator tree nodes expanding).
With all outdated metadata and with read-only data, maybe.

These settings will be disabled in the scope of "Disable extra metadata reading" enabling:

Metadata: Show row count for tables
Editors: Force object refresh on editor open
Data Editor: Read table metadata (unique keys)
Data Editor: Read table references (foreign keys)
SQL Editor: Save/restore active schema
Code editor: Read database table/columns for semantic analysis
SQL Processing: Refresh active schema after SQL Execution