id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
1026	&& vs. &&& what's the difference	robe	pramsey	"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);


}}}


"	defect	closed	medium	PostGIS 2.0.0	postgis	trunk	fixed