paleolimbot commented on issue #155: URL: https://github.com/apache/sedona-db/issues/155#issuecomment-3339880061
Hmm...that's a great point 😬 . It's normal for the planner to do *some* guessing, such as `ST_GeomFromText(NULL)`. In `ST_SetCrs()`'s case, it would be ambiguous whether that should return a geography or geometry with the CRS set (as it can handle both as input). I think we'd like to do `NULL::GEOMETRY` or `NULL::GEOGRAPHY` but that won't work (no SQL type names). The null handling for some of the other functions that accept geometry/geography as input probably have this problem, too (e.g., `ST_Intersection(NULL, NULL)` I bet would get you a geography today). Luckily I don't think that's particularly common. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
