BUG? DBeaver Version 25.3.3 + DuckDB v.1.4.x - memory -> main -> Tables empty

[jimdickson007]

Entirely possible this is user error but I have 2 Drivers for
DuckDB = duckdb_jdbc-1.3.2.1.jar
DuckDB_v1.4 = duckdb_jdbc-1.4.4.0.jar

I have 2 Connections
DuckDB_v.1.3.2
DuckDB_v1.4.x

The following script runs fine in both connections.
But table visible only in DuckDB_v.1.3.2 connection.

select version() ;

drop   table if exists table1 ;
create table table1 ( col1 int, col2 int, value1 varchar ) ;
insert into table1 ( col1, col2, value1 ) values ( 3, 4, 'table1' ) ;

describe table1 ;
select * from table1 ;

> select version() 

"version"()|
-----------+
v1.3.2     |

1 row(s) fetched.


> describe table1 

column_name|column_type|null|key|default|extra|
-----------+-----------+----+---+-------+-----+
col1       |INTEGER    |YES |   |       |     |
col2       |INTEGER    |YES |   |       |     |
value1     |VARCHAR    |YES |   |       |     |

3 row(s) fetched.


> select * from table1 

col1|col2|value1|
----+----+------+

0 row(s) fetched.


> select version() 

"version"()|
-----------+
v1.4.4     |

1 row(s) fetched.


> describe table1 

column_name|column_type|null|key|default|extra|
-----------+-----------+----+---+-------+-----+
col1       |INTEGER    |YES |   |       |     |
col2       |INTEGER    |YES |   |       |     |
value1     |VARCHAR    |YES |   |       |     |

3 row(s) fetched.


> select * from table1 

col1|col2|value1|
----+----+------+

0 row(s) fetched.

Any advice appreciated

[jimdickson007]

NB Believe I saw same in DataGrip but occurs for both DuckDB v1.3 & 1.4 so different issues ( DataGrip does not fully support DuckDB and suspect each click opens a new session )

[LonwoLonwo]

Did you try to refresh the "main" node after tables creation?
Also, do you use two connections for one node or each connection to a separate database file?

[jimdickson007]

Refresh - yes
Two connections - each has different driver version. Both use inmemory ( so no database file ). Does that answer your question? Can post screenshots if necessary.
Aside from possible user error, possible that DuckDB has changed how introspection / data dictionary / information_schema works ( I don't know enough to test ).

If there is any evidence that this is a DuckDB issue ( not DBeaver ) will log with them but as things stand cannot use DBeaver & DuckDB 1.4.x ( which is their LTS version )

-----------



-----------



-----------



-----------

[jimdickson007]

Workaround here : duckdb/duckdb#21580

[LonwoLonwo]

Thanks for the investigation