Allow usage of subselects as PSQL expressions [CORE2580] #2990
Assignees
Comments
Modified by: @asfernandesassignee: Adriano dos Santos Fernandes [ asfernandes ] |
Modified by: @dyemanovissuetype: New Feature [ 2 ] => Improvement [ 4 ] |
Modified by: @asfernandesstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 2.5 RC1 [ 10362 ] |
Modified by: @pavel-zotovQA Status: No test |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] QA Status: No test => Done successfully Test Details: Tes is not needed: there are already lot of other tests which does use this functionality. |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] Test Details: Tes is not needed: there are already lot of other tests which does use this functionality. => Test is not needed: there are already lot of other tests which does use this functionality. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Submitted by: @asfernandes
Is related to QA321
Curently, subselects can't be used as PSQL expressions, and all these constructions result in error:
var = (select ... from ...);
if ((select ... from ...) = 1) then
if (1 = any (select ... from ...)) then
if (1 in (select ... from ...)) then
These are all potentially valid expressions. Now the user need to write independents SELECT ... INTO without any advantage.
Commits: a8c1cdb
====== Test Details ======
Test is not needed: there are already lot of other tests which does use this functionality.
The text was updated successfully, but these errors were encountered: