[rjb32]

Read the components of a point.

[rjb32]

Note

AI-generated summary.

Summary

Goal. Read a point's fields: p.x, p.y, p.z, p.longitude, p.latitude, p.height, p.crs and p.srid, on a variable, a property (n.at.latitude), a point inside a list, and in a map projection (p {.longitude, .crs}).

Approach. The analyzer treats a point like a datetime or a duration: PointPart is resolved at analysis and each part lowers to one op (db.point_x ... db.point_srid), following the datetime component ops. A part's type depends on the part: a coordinate is a double, crs a string, srid an integer. p.z on a 2D point and p.latitude on a cartesian one raise on that row, as in Neo4j, so those four ops are MayRaise and never speculatable. A point inside a tagged cell is read through the map-key path, which now knows points.

Where to look.

• query/analyzer/ExprAnalyzer.cpp:573: the component branch that now covers points
• query/ir/dialect/db/DBOps.td:3056 PointZ: why four of the eight ops may raise
• storage/columns/Functions.h:611 PointComponentFunction: the per-row read
• query/ir/exec/NLExecutor.cpp:5679 pointComponentCell: p.x on a tagged cell

 readStaticKey(keyed)
   DateTime -> componentCell(instant)
   Duration -> componentCell(duration)
+  Point    -> pointComponentCell(point)

Evidence

• Before: WITH point({x: 1, y: 2}) AS p RETURN p.x has no point component to read.
  After:

  test_query_ir_point_component   [  PASSED  ] 15 tests.
  map projection, temporal map projection, datetime and duration component suites: 14/14 passed
  

Merge Danger

Door: two-way

Blast Radius: query

The "map projection reads ..." error now lists points; the two tests that pin it are updated.