UNION processing #80
-
Hi Bruce, SELECT 1 The current version chunks the code into two sections and removes the second UNION. So when I execute it, it produced two result sets rather than just 1. Is there a setting anywhere that the whole UNIONs code to be kept in a single section? I have some SQL code provided by others that contains 10-20 UNIONs all together. The produced multiple result sets at the moment. I appreciate your comments, and thank you again. Here is the output I feed the above SQL into the parser. Start... Statement 2: select 3 Regards |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
Thank you for posting this. I'll look into it and get back to you. |
Beta Was this translation helpful? Give feedback.
-
I've verified that it's not working as I would expect, so created an issue, #81 . I've got a large amount of changes sitting in the dev branch, so I'll work on how to resolve as well as see what of those changes can be released versus left out for now. |
Beta Was this translation helpful? Give feedback.
-
Resolved in latest release, https://www.nuget.org/packages/TSQL.Parser/2.0.0 . Example syntax, https://dotnetfiddle.net/kL5Uxw . |
Beta Was this translation helpful? Give feedback.
Resolved in latest release, https://www.nuget.org/packages/TSQL.Parser/2.0.0 .
Example syntax, https://dotnetfiddle.net/kL5Uxw .