paleolimbot commented on PR #1162:
URL: https://github.com/apache/sedona-db/pull/1162#issuecomment-5299994790

   > Should I modify this PR to only add ST_Force3DZ
   
   That would be great...I didn't catch this when it was added, but for this 
kind of thing I also don't mind not porting older PostGIS functions with newer 
recommended behaviour. PostGIS and Sedona Spark are both useful guides with a 
longer user base to draw on than we have here (and make CI/review easier 
because of the parity check), I'm just trying to avoid porting unintentional 
behaviour from either while we're taking the time to review and test it all.


-- 
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]

Reply via email to