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

Sub-optimal (not indexed) query plan for outer joins involving complex views [CORE2659] #3065

Closed
firebird-automations opened this issue Oct 3, 2009 · 4 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @dyemanov

Under some conditions (without a simple test case, unfortunately), if (a) some view contains unions/aggregations inside, (b) this view has expression based columns and (c) this view is used in outer joins with other streams and the join condition involves the view columns (expressions), then an outer join may be optimized badly.

Commits: 3a3512d

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

assignee: Dmitry Yemanov [ dimitr ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 2.5 RC1 [ 10362 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

status: Resolved [ 5 ] => Closed [ 6 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

status: Closed [ 6 ] => Closed [ 6 ]

QA Status: Not enough information

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment