#924 closed defect (wontfix)
GEOMETRYCOLLECTION(EMPTY) breaking change
| Reported by: | robe | Owned by: | pramsey |
|---|---|---|---|
| Priority: | medium | Milestone: | PostGIS 2.0.0 |
| Component: | postgis | Version: | master |
| Keywords: | Cc: |
Description
This is a related ticket to #923.
As Mike noted, we broke backwards compatibility with
GEOMETRYCOLLECTION(EMPTY).
— this used to be legal in PostGIS 1.5 and below but in 2.0 now throws and error SELECt ST_IsEmpty('GEOMETRYCOLLECTION(EMPTY)'::geometry);
— FWIW GEOMETRYCOLLECTION(EMPTY) is illegal in SQL Server as well and GEOMETRYCOLLECTION EMPTY works fine.
Is this an intentional break or an accidental one? If so as Mike states we should document that as a break. Not sure if it really affects anybody though.
Change History (2)
comment:1 by , 14 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
comment:2 by , 14 years ago
document warning added at r7447 (for ST_IsEmpty and ST_GeomFromText functions)
Note:
See TracTickets
for help on using tickets.
Sure, can document break… I doubt it affects anyone.