buraksenn commented on PR #21416: URL: https://github.com/apache/datafusion/pull/21416#issuecomment-4267296970
> > This is a question actually I've checked behaviors of Postgresql and Duckdb about null semantics and continued with the Postgresql behavior. However, I'm not sure if we want this so also put Duckdb outputs. It would be great to have feedback on this > > I agree with following postgres semantics; to me it seems more intuitive and inline with other null operation semantics, and off the top of my head I _think_ DataFusion tries to follow postgres more closely though I may be remembering incorrect (or out of date). > > I haven't fully reviewed this PR, since it seems to change both the null semantics for `any` whilst also introducing `all` support. It might be a good idea to split these into separate PRs to more them easier to review. Thanks @Jefffrey for checking this PR. I've combined ANY operator logic to not cause duplication but I understand it makes sense to separate PRs. Thus, I've narrowed down PR scope to only include `ALL` operator support with Postgres null handling and then will open a followup PR for `ANY` operator -- 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]
