Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Clarify semantics of columns().select() versus set() for INSERT ... SELECT statements #510
I posted an example at http://stackoverflow.com/q/18816748/14731 which shows that QueryDSL allows users to form invalid queries.
It turns out that I needed to replace
Expected behavior: QueryDSL should either prevent construction of invalid queries (compile or runtime failure) or translate
There is also the outstanding question of why QueryDSL is injecting
Querydsl inserts dual because it is defined as the dummy table for H2. Does it affect the query semantics?
Both options are syntactically valid INSERT clauses, but with different semantics.
you will get the conditional insertion you are aiming for and with
you will get null values, if the sub query doesn't return any rows.
So I suggest to fix this issue on the documentation level.
added a commit
Sep 18, 2013
This runs for a while, then fails with: