[postgis-tickets] [PostGIS] #5546: ERROR: operator is not unique: topogeometry <> topogeometry

[PostGIS]

#5546: ERROR:  operator is not unique: topogeometry <> topogeometry
-----------------------+---------------------------
  Reporter:  strk      |      Owner:  strk
      Type:  defect    |     Status:  closed
  Priority:  blocker   |  Milestone:  PostGIS 3.5.0
 Component:  topology  |    Version:  master
Resolution:  wontfix   |   Keywords:  regression
-----------------------+---------------------------
Changes (by strk):

 * status:  assigned => closed
 * resolution:   => wontfix

Comment:

 So the new information is that there is an implicit cast to "record", even
 if not shown by the `\dC` psql command.

 This means the ambiguity is between comparing the TopoGeometry objects as
 if they were records or comparing them as if they were geometries. Pretty
 big ambiguity and it's even a much different cost (compare as geometry is
 going to be expensive).

 The downstream code (pgtopo_update_sql) expected to compare as record, so
 to fix the regression we would need to add TopoGeometry inequality
 operator to compare the integer values of the type, but as the equality
 operator (`=`) was also ambiguous in 3.0, I'd rather keep it ambiguous for
 now and not consider this a regression.
-- 
Ticket URL: <https://trac.osgeo.org/postgis/ticket/5546#comment:8>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.