[
https://issues.apache.org/jira/browse/ASTERIXDB-1560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15406520#comment-15406520
]
Michael J. Carey commented on ASTERIXDB-1560:
---------------------------------------------
Thx! Meanwhile, regarding the last/long comment - COOL! That actually raises
an orthogonal issue - perhaps we should (someday) add ANY as a supported
typename and then you wouldn't need two separate mechanisms. (We'd have a
type-system-supported way of having fields with known names but variable types.)
> Misleading SQL++ error message when variables are undefined
> ------------------------------------------------------------
>
> Key: ASTERIXDB-1560
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-1560
> Project: Apache AsterixDB
> Issue Type: Bug
> Components: AsterixDB, Error Reporting
> Reporter: Michael J. Carey
> Assignee: Yingyi Bu
> Priority: Minor
>
> This query:
> SELECT u.name AS uname, m.message AS message
> FROM GleambookUsers u
> UNNEST GleambookMessages m
> WHERE m.authorId = user.id;
> Yields this error message:
> Cannot resolve ambiguous alias (variable) reference for identifier user
> [AlgebricksException]
> The reference is undefined, not ambiguous, in this case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
