fixed issue in query adapter's queryList where CompoundSelectStatemen…#781
fixed issue in query adapter's queryList where CompoundSelectStatemen…#781mthongvanh wants to merge 1 commit into
Conversation
…t is not executed
|
Is there an open issue for this PR? |
|
Hi Dmytro,
There's not currently an open issue. We just saw an issue recently after updating our fork. Should I create an issue first?
…On Wed, Sep 20, 2023 at 10:12 Dmytro Puzak ***@***.***> wrote:
Is there an open issue for this PR?
—
Reply to this email directly, view it on GitHub
<#781 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABF3HYDEABSVW7CRRA4PPW3X3KQORANCNFSM6AAAAAA466TLOU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Please add a sample code that does not work in the current Floor version and a relevant explanation of the issue. |
|
Floor version 1.4.2 Issue: Fix: Sample Code |
|
@mthongvanh @Query('SELECT message FROM Task UNION SELECT message FROM Task')
Future<List<String>> queryMessages(); |
…t is not executed
queryList does not allow compound select statements to be executed. UNION queries throw state errors.
updating the rootNode's type check to BaseSelectStatement instead of SelectStatement fixes the issue.