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.

Sign up for GitHub

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

Jump to bottom

Standard compliance for computed fields syntax/semantics [CORE1407] #1825

Open
firebird-automations opened this issue Aug 7, 2007 · 3 comments
Open

Standard compliance for computed fields syntax/semantics [CORE1407] #1825

firebird-automations opened this issue Aug 7, 2007 · 3 comments
Labels
component: engine priority: minor type: improvement

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @dyemanov

Is related to CORE1385
Is related to CORE1386
Jira_subtask_outward CORE5168

Votes: 5

Accordingly to the SQL:2003 specification:

1) Either <data type> or <domain name> are allowed in the computed field declaration, but Firebird supports only <data type> there.
2) <column constraint definition> should belong to computed and identity fields as well as to stored ones.
3) <collate clause> should belong to computed and identity fields as well as to stored ones.

[ appropriate sub-tasks will be created for this ticket ]
@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

Link: This issue is related to CORE1385 [ CORE1385 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

Link: This issue is related to CORE1386 [ CORE1386 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

Workflow: jira [ 12771 ] => Firebird [ 13905 ]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
component: engine priority: minor type: improvement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@firebird-automations