[
https://issues.apache.org/jira/browse/ASTERIXDB-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16160496#comment-16160496
]
ASF subversion and git services commented on ASTERIXDB-2050:
------------------------------------------------------------
Commit 8c6e7cdb66f21cd34901f45ac8fb5768d82964b4 in asterixdb's branch
refs/heads/master from [~mhubail]
[ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=8c6e7cd ]
[ASTERIXDB-2050][SQL] Update Docs to Reflect New SQL++ Model
- user model changes: no
- storage format changes: no
- interface changes: no
Details:
- Update docs to reflect the new enforcement of semicolon
after every statement.
- Add missing semicolons to SET statements in examples.
Change-Id: I31ed7413a6de028fa9d1a0a9d2c6b36ac39ff9c9
Reviewed-on: https://asterix-gerrit.ics.uci.edu/1996
Sonar-Qube: Jenkins <[email protected]>
Tested-by: Jenkins <[email protected]>
Contrib: Jenkins <[email protected]>
Integration-Tests: Jenkins <[email protected]>
Reviewed-by: Till Westmann <[email protected]>
> Enforce a Semicolon After Each SQL++ Statement
> ----------------------------------------------
>
> Key: ASTERIXDB-2050
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2050
> Project: Apache AsterixDB
> Issue Type: Improvement
> Components: SQL - Translator SQL++
> Reporter: Murtadha Hubail
> Assignee: Murtadha Hubail
>
> Currently, only queries must be followed by a semicolon in SQL++ and it's
> optional to follow DDLs/DMLs with one. While this gives some flexibly to the
> user, it could lead to many unintentional errors and ambiguity.
> For example, when this is executed:
> {code:java}
> create dataverse x + 1 + 1;
> {code}
> The dataverse 'x' will be created and the following will be returned:
> {code:java}
> 2
> {code}
> The proposed solution to eliminate this ambiguity is to enforce a semicolon
> after every SQL++ statement.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
