[postgis-devel] BOX3D strange behaviour
strk at keybit.net
Fri Feb 26 07:33:41 PST 2016
On Fri, Feb 26, 2016 at 06:41:04AM -0500, Daniel Baston wrote:
> There's now a pull request to address this:
> The only places in the regression suite where a BOX3D->geometry cast is
> executed are places where a (user-input) BOX3D literal is explicitly cast
> to a geometry. So, there shouldn't be a performance hit or ill effect of
> having the BOX3D->geometry cast produce a PolyhedralSurface, as Even
> Any objections to this?
I think it'd still count as an API break as clients expecting
a POLYGON would not get one. Hard to anticipate how offending
such change could be, but should be threated as an API break,
I wonder if it makes sense to keep improving BOX3D rather than
deprecating it in favor of something different.
More information about the postgis-devel