Opened 13 years ago
Closed 13 years ago
#1458 closed defect (fixed)
unstable results from st_orderingequals (again!)
Reported by: | strk | Owned by: | pramsey |
---|---|---|---|
Priority: | blocker | Milestone: | PostGIS 2.0.0 |
Component: | postgis | Version: | master |
Keywords: | Cc: |
Description
strk=# \a \t Output format is unaligned. Showing only tuples. strk=# select st_orderingequals('POINT EMPTY', 'POINT EMPTY'); f strk=# select st_orderingequals('POINT EMPTY', 'POINT EMPTY'); t
In case you don't see it: first call returns FALSE, second call returns TRUE. Calls are perfectly identical.
Change History (5)
comment:1 by , 13 years ago
comment:3 by , 13 years ago
NOTICE: bbox1:0x7fd547e5cfb0, bbox2:0x7fd547e5d0b0 NOTICE: [lwgeom.c:lwgeom_same:494] bounding boxes differ
It makes no sense for POINT EMPTY to have a non-NULL bbox pointer in LWGEOM. That must be the issue.
comment:4 by , 13 years ago
Deserializer's fault, where gserialized_read_gbox_p computes the BOX for an empty point, _assuming_ there are points… It instead reads garbage and possibly return different data.
Note:
See TracTickets
for help on using tickets.
casting text to geometry returns true at first go