Opened 9 years ago

Closed 9 years ago

## #1026 closed defect (fixed)

# && vs. &&& what's the difference

Reported by: | robe | Owned by: | pramsey |
---|---|---|---|

Priority: | medium | Milestone: | PostGIS 2.0.0 |

Component: | postgis | Version: | master |

Keywords: | Cc: |

### Description

These seem to be exactly the same in my installs shouldn't one be a 2d interacts check and the other a 3D interacts check?

The definitions look the same and when testing they seem to give the same answers with 3D geometries even in cases where I expect &&& to return false and && to return true

e.g. both have:

CREATE OPERATOR &&&( PROCEDURE = geometry_overlaps, LEFTARG = geometry, RIGHTARG = geometry, COMMUTATOR = &&&, RESTRICT = contsel, JOIN = contjoinsel); CREATE OPERATOR &&( PROCEDURE = geometry_overlaps, LEFTARG = geometry, RIGHTARG = geometry, COMMUTATOR = &&, RESTRICT = contsel, JOIN = contjoinsel);

### Change History (4)

### comment:2 Changed 9 years ago by

Nope I get a ERROR: function geometry_overlaps_nd(geometry, geometry) does not exist

when I try that

**Note:**See TracTickets for help on using tickets.