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

Add support for SQL standard UNION syntax. jOOQ's current understanding of UNION is just convenience #1658

Closed
lukaseder opened this issue Aug 1, 2012 · 1 comment

Comments

@lukaseder
Copy link
Member

The SQL standard expects the UNION operator (and other set operations) to stand between unordered "subselects". Only the whole UNION expression can then be ordered (and maybe limited). This should be reflected in the jOOQ API, correctly. Today's implementation is wrong, strictly speaking, although it may sometimes be more convenient

@lukaseder lukaseder modified the milestones: Version 3.4.0, Version 3.3.0 Feb 5, 2014
@lukaseder
Copy link
Member Author

This issue is very complex to implement and would make #2694 and #2335 much harder to implement. We should wait with this improvement

@lukaseder lukaseder modified the milestones: Version 3.5.0, Version 3.4.0 May 8, 2014
lukaseder added a commit that referenced this issue Aug 22, 2014
lukaseder added a commit that referenced this issue Aug 22, 2014
lukaseder added a commit that referenced this issue Oct 30, 2014
lukaseder added a commit that referenced this issue Nov 20, 2014
…entheses placed around <query expression body>
lukaseder added a commit that referenced this issue Nov 21, 2014
arnaudroger pushed a commit to arnaudroger/jOOQ that referenced this issue Dec 16, 2014
… parentheses placed around <query expression body>
arnaudroger pushed a commit to arnaudroger/jOOQ that referenced this issue Dec 16, 2014
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

1 participant