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

Jump to bottom

SQL2003 Standard syntax is still not fully supported [CORE2489] #2902

Closed
firebird-automations opened this issue Jun 2, 2009 · 4 comments
Closed

SQL2003 Standard syntax is still not fully supported [CORE2489] #2902

firebird-automations opened this issue Jun 2, 2009 · 4 comments
Labels
affect-version: 1.5.4 affect-version: 1.5.5 affect-version: 2.0.0 affect-version: 2.0.1 affect-version: 2.0.2 affect-version: 2.0.3 affect-version: 2.0.4 affect-version: 2.0.5 affect-version: 2.1.0 affect-version: 2.1.1 affect-version: 2.1.2 component: engine priority: major resolution: duplicate type: sub-task

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: Ain Valtin (ain)

Jira_subtask_inward CORE711

AFAICS the fix only includes the table name part of the syntax, but not the FOR EACH { ROW | STATEMENT } and other parts... so IMO it really can't be considered as being fixed.
There is also another ticket requesting the FOR EACH STATEMENT part of the syntax : CORE1268
@firebird-automations
Copy link
Collaborator Author

Commented by: @dyemanov

The original request was about the syntax, while you request different semantics (already registered as CORE1268). Please don't treat the ticket caption so wide, it was just about syntactic sugar. I'm going to reject this sub-task as being not really related to its parent.

@firebird-automations
Copy link
Collaborator Author

Commented by: @asfernandes

Agreed, there is no reason for that sub-task.

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

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

resolution: Duplicate [ 3 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
affect-version: 1.5.4 affect-version: 1.5.5 affect-version: 2.0.0 affect-version: 2.0.1 affect-version: 2.0.2 affect-version: 2.0.3 affect-version: 2.0.4 affect-version: 2.0.5 affect-version: 2.1.0 affect-version: 2.1.1 affect-version: 2.1.2 component: engine priority: major resolution: duplicate type: sub-task
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@firebird-automations