neilconway commented on issue #22266: URL: https://github.com/apache/datafusion/issues/22266#issuecomment-4519478459
My two cents, on the topic of Postgres compatibility / SQL dialect in general: * I think the SQL standard is a good place to start. In most situations, that is what Postgres follows, usually unless there is a good reason to deviate. * I think that's a reasonable rule of thumb for us as well: follow the SQL spec and/or Postgres in most circumstances / as a reasonable default, but if there is a good reason to deviate, that can be justified. As far as when to preserve existing behavior, I think DataFusion's current behavior in a lot of corner cases is either unintentional or actively buggy (#14612, #14272, #15161 are a few examples that come to mind in just type coercion!). SQL is a large and complex language and DF's implementation is relatively new -- there will (hopefully!) be many more new users in DataFusion in the coming years than there are today :) So while I think we should be aware of SQL backward compatibility and try to ease migration pain as much as we can (e.g., clear release notes / upgrade guidance, config flags when necessary), I do think evolving the SQL dialect to be more consistent and standards-conformant is a good thing. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
