seddonm1 commented on pull request #9108: URL: https://github.com/apache/arrow/pull/9108#issuecomment-755792827
> I agree with @seddonm1 that ideally we would follow Postgres when possible so we can just re-use all their documentation and semantics and so we don't end up inadvertently creating yet another SQL dialect like spark. > > Specifically in this case, it looks like the relevant postgres function is called `TRIM`. A screen shot from https://www.postgresql.org/docs/9.1/functions-string.html FYI (because I had to work this out) the way to read the Postgres documentation the first table (Table 9-6. SQL String Functions and Operators) is the ANSI SQL and the second table (Table 9-7. Other String Functions) are Postgres dialect specific implementations. This pattern is standardised for other Postgres documentation. You can see that `ltrim` comes from the Table 9-7. Other String Functions section. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
