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
CREATE VIEW as SELECT .... [CORE831] #1219
Comments
Modified by: @dyemanovComponent: Engine [ 10000 ] |
Modified by: @pcisarassignee: Dmitry Yemanov [ dimitr ] => |
Modified by: @dyemanovstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 2.1 [ 10041 ] assignee: Dmitry Yemanov [ dimitr ] |
Modified by: @pcisarWorkflow: jira [ 11041 ] => Firebird [ 14352 ] |
Commented by: @pmakowski Q/A tested |
Modified by: @pmakowskistatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @pavel-zotovQA Status: No test |
Modified by: @pavel-zotovstatus: Closed [ 6 ] => Closed [ 6 ] QA Status: No test => Covered by another test(s) Test Details: There are lot of tests where such syntax is used. |
Submitted by: Valdir Stiebe Junior (ogecrom)
Is duplicated by CORE1078
Is related to QA121
When creating a view, it would be easier if we could use the following syntax:
create view V_NAME as
select
T1.FIELD1,
T1.FIELD1 COLUMN_ALIAS1,
T1.FIELD1 COLUMN_ALIAS2
from
TABLE1 T1
instead of
create view V_NAME (FIELD1, COLUMN_ALIAS1, COLUMN_ALIAS2) as
select ...
Since a select command can't repeat a column alias, this field list could be optional.
And it will be much easier to store view definitions on some database modelling tools.
Commits: d5b27fd
====== Test Details ======
There are lot of tests where such syntax is used.
The text was updated successfully, but these errors were encountered: