Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for full set of operators in left outer join on clause #268

Open
dakotahNorth opened this issue Nov 1, 2022 · 0 comments
Open

Comments

@dakotahNorth
Copy link

dakotahNorth commented Nov 1, 2022

Esper documentation states

If the optional on clause is specified, it may only employ the = equals operator and property names.
Any other operators must be placed in the where-clause. The stream names that appear in the
on clause may refer to any stream in the from-clause

resulting in different results when the where-clause is used because the on-clause only supports ='s since the semantics are different.

From https://stackoverflow.com/questions/4752455/left-join-with-where-clause

When making OUTER JOINs (ANSI-89 or ANSI-92), filtration location matters because criteria specified in the ON clause is applied before the JOIN is made. Criteria against an OUTER JOINed table provided in the WHERE clause is applied after the JOIN is made. This can produce very different result sets. In comparison, it doesn't matter for INNER JOINs if the criteria is provided in the ON or WHERE clauses -- the result will be the same.

This feature request is to add full support for other operators within the on clause.

@dakotahNorth dakotahNorth changed the title Add support for binary results in left outer join on clause Add support for full set of operators in left outer join on clause Nov 1, 2022
@dakotahNorth dakotahNorth changed the title Add support for full set of operators in left outer join on clause Support for full set of operators in left outer join on clause Nov 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants