You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Export now reconstructs spatial (geometry/geography) column values with a
dialect-specific SQL expression instead of losing type information.
Spatial data preview: geometry/geography values are shown on an interactive map over
OpenStreetMap tiles - both in the Data Browser's cell preview and, for the SQL Console,
as a map overlay on the "Rows"/"Columns" result.
Supports points, lines, polygons and their multi-/collection variant.
Coordinate systems: WGS84 (SRID 4326/8307) and EPSG:3857 "Web Mercator" (the projection
used by web maps / online portals).
Navigation: drag to pan, mouse wheel to zoom (in the SQL Console the point under the
cursor stays fixed), Shift+drag to zoom into a box.
Geometries are drawn with a high-contrast outline/halo so they stay visible over any
map tiles; points render as a colored ring with a white center. Hovering a geometry in
the SQL Console highlights it and shows the row's data as a tooltip.
Legend (SQL Console): color the geometries by the values of a chosen column, pick a
color palette, adjust the legend text size, and move/resize the legend freely.
"Save as image": save the current map as a PNG/JPG/BMP/GIF file or copy it to the
clipboard (the move/resize handles are omitted from the exported image).
"Analyze SQL": proposed associations are now checked for partially covered primary keys.
If a proposal's join condition equates only some columns of a composite primary key on
table "A" or "B", that cell is flagged with a warning icon and a tooltip listing the
still-uncovered column(s).
"Analyze SQL": AssociationProposer now understands "NATURAL JOIN" and "JOIN ... USING
(col)" syntax and proposes associations for them, instead of silently ignoring those
joins.
Fixed: AssociationProposer could silently drop a column equality from a proposed join
condition when the same table appeared twice in a query under different aliases
(self-join), because equations from different aliases were incorrectly treated as
duplicates.