-
Notifications
You must be signed in to change notification settings - Fork 4k
Labels
x:clickhousexf:dataxf:gisxqa:check-cloudbeaverRequires Cloudbeaver testingRequires Cloudbeaver testing
Milestone
Description
Description
The release of DBeaver 25.0.1 introduced the rendering of Clickhouse geometries on the spatial viewer (aka map).
Version 25.0.1
This allowed Geometries in Clickhouse to rendered on a map, see example below:
select
cast(arrayJoin([(4.837388, 52.38795),
(4.951513, 52.354582),
(4.961987, 52.371763),
(4.870017, 52.334932),
(4.89813, 52.357238),
(4.852437, 52.370315),
(4.901712, 52.369567),
(4.874112, 52.339823),
(4.856942, 52.339122),
(4.870253, 52.360353)]
)
as Point) as Pointwhich would result in the following map:
After Version 25.0.1
The same query on updated versions of DBeaver (specifically 25.2.0) now renders the points as Tuples, see below
It seems the data is rendered with what looks like an unknown datatype where before it rendered it as a geometry type
vs
This issues is related to this as I was asked by @E1izabeth to create an issue with reproducible steps.
DBeaver Version
25.2.0
Operating System
macOS 15.6.1
Database and driver
Steps to reproduce
Run this query
select
cast(arrayJoin([(4.837388, 52.38795),
(4.951513, 52.354582),
(4.961987, 52.371763),
(4.870017, 52.334932),
(4.89813, 52.357238),
(4.852437, 52.370315),
(4.901712, 52.369567),
(4.874112, 52.339823),
(4.856942, 52.339122),
(4.870253, 52.360353)]
)
as Point) as Pointand see result as tuples not geometries on a map

Additional context
No response
Metadata
Metadata
Assignees
Labels
x:clickhousexf:dataxf:gisxqa:check-cloudbeaverRequires Cloudbeaver testingRequires Cloudbeaver testing