getBounds fails for compound 3d crs in postgis jdbc store

Description

There is a test for this, but because of a mistake in the test setup Postgisdialect.getOptimizedBounds is skipped and instead a general getbounds is used.

The bug is in Postgisdialect.getOptimizedBounds where the CRS is not being flattened like in the generic code.

Environment

None

Activity

Show:
Niels Charlier
June 8, 2020, 1:03 PM

Fixed

Assignee

Niels Charlier

Reporter

Niels Charlier

Triage

None

Components

Fix versions

Priority

Medium
Configure