You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@asterixdb.apache.org by im...@apache.org on 2017/01/25 19:56:12 UTC
[02/11] asterixdb-site git commit: fix SQLPP/AQL function docs
http://git-wip-us.apache.org/repos/asf/asterixdb-site/blob/d5b11d83/docs/0.9.0/sqlpp/manual.html
----------------------------------------------------------------------
diff --git a/docs/0.9.0/sqlpp/manual.html b/docs/0.9.0/sqlpp/manual.html
new file mode 100644
index 0000000..845214f
--- /dev/null
+++ b/docs/0.9.0/sqlpp/manual.html
@@ -0,0 +1,4183 @@
+<!DOCTYPE html>
+<!--
+ | Generated by Apache Maven Doxia at 2017-01-25
+ | Rendered using Apache Maven Fluido Skin 1.3.0
+-->
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+ <head>
+ <meta charset="UTF-8" />
+ <meta name="viewport" content="width=device-width, initial-scale=1.0" />
+ <meta name="Date-Revision-yyyymmdd" content="20170125" />
+ <meta http-equiv="Content-Language" content="en" />
+ <title>AsterixDB – The SQL++ Query Language</title>
+ <link rel="stylesheet" href="../css/apache-maven-fluido-1.3.0.min.css" />
+ <link rel="stylesheet" href="../css/site.css" />
+ <link rel="stylesheet" href="../css/print.css" media="print" />
+
+
+ <script type="text/javascript" src="../js/apache-maven-fluido-1.3.0.min.js"></script>
+
+
+
+<script>(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
+ (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
+ m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
+ })(window,document,'script','//www.google-analytics.com/analytics.js','ga');
+
+ ga('create', 'UA-41536543-1', 'uci.edu');
+ ga('send', 'pageview');</script>
+
+ </head>
+ <body class="topBarDisabled">
+
+
+
+
+ <div class="container-fluid">
+ <div id="banner">
+ <div class="pull-left">
+ <a href=".././" id="bannerLeft">
+ <img src="../images/asterixlogo.png" alt="AsterixDB"/>
+ </a>
+ </div>
+ <div class="pull-right"> </div>
+ <div class="clear"><hr/></div>
+ </div>
+
+ <div id="breadcrumbs">
+ <ul class="breadcrumb">
+
+
+ <li id="publishDate">Last Published: 2017-01-25</li>
+
+
+
+ <li id="projectVersion" class="pull-right">Version: 0.9.0</li>
+
+ <li class="divider pull-right">|</li>
+
+ <li class="pull-right"> <a href="../index.html" title="Documentation Home">
+ Documentation Home</a>
+ </li>
+
+ </ul>
+ </div>
+
+
+ <div class="row-fluid">
+ <div id="leftColumn" class="span3">
+ <div class="well sidebar-nav">
+
+
+ <ul class="nav nav-list">
+ <li class="nav-header">Get Started - Installation</li>
+
+ <li>
+
+ <a href="../ncservice.html" title="Option 1: using NCService">
+ <i class="none"></i>
+ Option 1: using NCService</a>
+ </li>
+
+ <li>
+
+ <a href="../install.html" title="Option 2: using Managix">
+ <i class="none"></i>
+ Option 2: using Managix</a>
+ </li>
+
+ <li>
+
+ <a href="../yarn.html" title="Option 3: using YARN">
+ <i class="none"></i>
+ Option 3: using YARN</a>
+ </li>
+ <li class="nav-header">AsterixDB Primer</li>
+
+ <li>
+
+ <a href="../sqlpp/primer-sqlpp.html" title="Option 1: using SQL++">
+ <i class="none"></i>
+ Option 1: using SQL++</a>
+ </li>
+
+ <li>
+
+ <a href="../aql/primer.html" title="Option 2: using AQL">
+ <i class="none"></i>
+ Option 2: using AQL</a>
+ </li>
+ <li class="nav-header">Data Model</li>
+
+ <li>
+
+ <a href="../datamodel.html" title="The Asterix Data Model">
+ <i class="none"></i>
+ The Asterix Data Model</a>
+ </li>
+ <li class="nav-header">Queries - SQL++</li>
+
+ <li class="active">
+
+ <a href="#"><i class="none"></i>The SQL++ Query Language</a>
+ </li>
+
+ <li>
+
+ <a href="../sqlpp/builtins.html" title="Builtin Functions">
+ <i class="none"></i>
+ Builtin Functions</a>
+ </li>
+ <li class="nav-header">Queries - AQL</li>
+
+ <li>
+
+ <a href="../aql/manual.html" title="The Asterix Query Language (AQL)">
+ <i class="none"></i>
+ The Asterix Query Language (AQL)</a>
+ </li>
+
+ <li>
+
+ <a href="../aql/builtins.html" title="Builtin Functions">
+ <i class="none"></i>
+ Builtin Functions</a>
+ </li>
+ <li class="nav-header">Advanced Features</li>
+
+ <li>
+
+ <a href="../aql/similarity.html" title="Support of Similarity Queries">
+ <i class="none"></i>
+ Support of Similarity Queries</a>
+ </li>
+
+ <li>
+
+ <a href="../aql/fulltext.html" title="Support of Full-text Queries">
+ <i class="none"></i>
+ Support of Full-text Queries</a>
+ </li>
+
+ <li>
+
+ <a href="../aql/externaldata.html" title="Accessing External Data">
+ <i class="none"></i>
+ Accessing External Data</a>
+ </li>
+
+ <li>
+
+ <a href="../feeds/tutorial.html" title="Support for Data Ingestion">
+ <i class="none"></i>
+ Support for Data Ingestion</a>
+ </li>
+
+ <li>
+
+ <a href="../udf.html" title="User Defined Functions">
+ <i class="none"></i>
+ User Defined Functions</a>
+ </li>
+
+ <li>
+
+ <a href="../aql/filters.html" title="Filter-Based LSM Index Acceleration">
+ <i class="none"></i>
+ Filter-Based LSM Index Acceleration</a>
+ </li>
+ <li class="nav-header">API/SDK</li>
+
+ <li>
+
+ <a href="../api.html" title="HTTP API">
+ <i class="none"></i>
+ HTTP API</a>
+ </li>
+ </ul>
+
+
+
+ <hr class="divider" />
+
+ <div id="poweredBy">
+ <div class="clear"></div>
+ <div class="clear"></div>
+ <div class="clear"></div>
+ <a href=".././" title="AsterixDB" class="builtBy">
+ <img class="builtBy" alt="AsterixDB" src="../images/asterixlogo.png" />
+ </a>
+ </div>
+ </div>
+ </div>
+
+
+ <div id="bodyColumn" class="span9" >
+
+ <!-- ! Licensed to the Apache Software Foundation (ASF) under one
+ ! or more contributor license agreements. See the NOTICE file
+ ! distributed with this work for additional information
+ ! regarding copyright ownership. The ASF licenses this file
+ ! to you under the Apache License, Version 2.0 (the
+ ! "License"); you may not use this file except in compliance
+ ! with the License. You may obtain a copy of the License at
+ !
+ ! http://www.apache.org/licenses/LICENSE-2.0
+ !
+ ! Unless required by applicable law or agreed to in writing,
+ ! software distributed under the License is distributed on an
+ ! "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ ! KIND, either express or implied. See the License for the
+ ! specific language governing permissions and limitations
+ ! under the License.
+ ! --><h1>The SQL++ Query Language</h1>
+<div class="section">
+<h2><a name="Table_of_Contents"></a><a name="toc" id="toc">Table of Contents</a></h2>
+
+<ul>
+
+<li><a href="#Introduction">1. Introduction</a></li>
+
+<li><a href="#Expressions">2. Expressions</a>
+
+<ul>
+
+<li><a href="#Operator_expressions">Operator expressions</a>
+
+<ul>
+
+<li><a href="#Arithmetic_operators">Arithmetic operators</a></li>
+
+<li><a href="#Collection_operators">Collection operators</a></li>
+
+<li><a href="#Comparison_operators">Comparison operators</a></li>
+
+<li><a href="#Logical_operators">Logical operators</a></li>
+ </ul></li>
+
+<li><a href="#Case_expressions">Case expressions</a></li>
+
+<li><a href="#Quantified_expressions">Quantified expressions</a></li>
+
+<li><a href="#Path_expressions">Path expressions</a></li>
+
+<li><a href="#Primary_expressions">Primary expressions</a>
+
+<ul>
+
+<li><a href="#Literals">Literals</a></li>
+
+<li><a href="#Variable_references">Variable references</a></li>
+
+<li><a href="#Parenthesized_expressions">Parenthesized expressions</a></li>
+
+<li><a href="#Function_call_expressions">Function call expressions</a></li>
+
+<li><a href="#Constructors">Constructors</a></li>
+ </ul></li>
+ </ul></li>
+
+<li><a href="#Queries">3. Queries</a>
+
+<ul>
+
+<li><a href="#SELECT_statements">SELECT statements</a></li>
+
+<li><a href="#Select_clauses">SELECT clauses</a>
+
+<ul>
+
+<li><a href="#Select_element">Select element/value/raw</a></li>
+
+<li><a href="#SQL_select">SQL-style select</a></li>
+
+<li><a href="#Select_star">Select *</a></li>
+
+<li><a href="#Select_distinct">Select distinct</a></li>
+
+<li><a href="#Unnamed_projections">Unnamed projections</a></li>
+
+<li><a href="#Abbreviatory_field_access_expressions">Abbreviatory field access expressions</a></li>
+ </ul></li>
+
+<li><a href="#Unnest_clauses">UNNEST clauses</a>
+
+<ul>
+
+<li><a href="#Inner_unnests">Inner unnests</a></li>
+
+<li><a href="#Left_outer_unnests">Left outer unnests</a></li>
+
+<li><a href="#Expressing_joins_using_unnests">Expressing joins using unnests</a></li>
+ </ul></li>
+
+<li><a href="#From_clauses">FROM clauses</a>
+
+<ul>
+
+<li><a href="#Binding_expressions">Binding expressions</a></li>
+
+<li><a href="#Multiple_from_terms">Multiple from terms</a></li>
+
+<li><a href="#Expressing_joins_using_from_terms">Expressing joins using from terms</a></li>
+
+<li><a href="#Implicit_binding_variables">Implicit binding variables</a></li>
+ </ul></li>
+
+<li><a href="#Join_clauses">JOIN clauses</a>
+
+<ul>
+
+<li><a href="#Inner_joins">Inner joins</a></li>
+
+<li><a href="#Left_outer_joins">Left outer joins</a></li>
+ </ul></li>
+
+<li><a href="#Group_By_clauses">GROUP BY clauses</a>
+
+<ul>
+
+<li><a href="#Group_variables">Group variables</a></li>
+
+<li><a href="#Implicit_group_key_variables">Implicit group key variables</a></li>
+
+<li><a href="#Implicit_group_variables">Implicit group variables</a></li>
+
+<li><a href="#Aggregation_functions">Aggregation functions</a></li>
+
+<li><a href="#SQL-92_aggregation_functions">SQL-92 aggregation functions</a></li>
+
+<li><a href="#SQL-92_compliant_gby">SQL-92 compliant GROUP BY aggregations</a></li>
+
+<li><a href="#Column_aliases">Column aliases</a></li>
+ </ul></li>
+
+<li><a href="#Where_having_clauses">WHERE clauases and HAVING clauses</a></li>
+
+<li><a href="#Order_By_clauses">ORDER BY clauses</a></li>
+
+<li><a href="#Limit_clauses">LIMIT clauses</a></li>
+
+<li><a href="#With_clauses">WITH clauses</a></li>
+
+<li><a href="#Let_clauses">LET clauses</a></li>
+
+<li><a href="#Union_all">UNION ALL</a></li>
+
+<li><a href="#Vs_SQL-92">SQL++ Vs. SQL-92</a></li>
+ </ul></li>
+
+<li><a href="#Errors">4. Errors</a>
+
+<ul>
+
+<li><a href="#Syntax_errors">Syntax errors</a></li>
+
+<li><a href="#Parsing_errors">Identifier resolution errors</a></li>
+
+<li><a href="#Type_errors">Type errors</a></li>
+
+<li><a href="#Resource_errors">Resource errors</a></li>
+ </ul></li>
+
+<li><a href="#DDL_and_DML_statements">5. DDL and DML statements</a>
+
+<ul>
+
+<li><a href="#Declarations">Declarations</a></li>
+
+<li><a href="#Lifecycle_management_statements">Lifecycle management statements</a>
+
+<ul>
+
+<li><a href="#Dataverses">Dataverses</a></li>
+
+<li><a href="#Datasets">Datasets</a></li>
+
+<li><a href="#Types">Types</a></li>
+
+<li><a href="#Functions">Functions</a></li>
+ </ul></li>
+
+<li><a href="#Modification_statements">Modification statements</a>
+
+<ul>
+
+<li><a href="#Inserts">Inserts</a></li>
+
+<li><a href="#Upserts">Upserts</a></li>
+
+<li><a href="#Deletes">Deletes</a></li>
+ </ul></li>
+ </ul></li>
+
+<li><a href="#Reserved_keywords">Appendix 1. Reserved keywords</a></li>
+</ul>
+<!-- ! Licensed to the Apache Software Foundation (ASF) under one
+ ! or more contributor license agreements. See the NOTICE file
+ ! distributed with this work for additional information
+ ! regarding copyright ownership. The ASF licenses this file
+ ! to you under the Apache License, Version 2.0 (the
+ ! "License"); you may not use this file except in compliance
+ ! with the License. You may obtain a copy of the License at
+ !
+ ! http://www.apache.org/licenses/LICENSE-2.0
+ !
+ ! Unless required by applicable law or agreed to in writing,
+ ! software distributed under the License is distributed on an
+ ! "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ ! KIND, either express or implied. See the License for the
+ ! specific language governing permissions and limitations
+ ! under the License.
+ ! -->
+<h1><a name="Introduction" id="Introduction">1. Introduction</a><font size="3" /></h1>
+<p>This document is intended as a reference guide to the full syntax and semantics of the SQL++ Query Language, a SQL-inspired language for working with semistructured data. SQL++ has much in common with SQL, but some differences do exist due to the different data models that the two languages were designed to serve. SQL was designed in the 1970’s for interacting with the flat, schema-ified world of relational databases, while SQL++ is much newer and targets the nested, schema-optional (or even schema-less) world of modern NoSQL systems.</p>
+<p>In the context of Apache AsterixDB, SQL++ is intended for working with the Asterix Data Model (<a href="../datamodel.html">ADM</a>),a data model based on a superset of JSON with an enriched and flexible type system. New AsterixDB users are encouraged to read and work through the (much friendlier) guide “<a href="primer-sqlpp.html">AsterixDB 101: An ADM and SQL++ Primer</a>” before attempting to make use of this document. In addition, readers are advised to read through the <a href="../datamodel.html">Asterix Data Model (ADM) reference guide</a> first as well, as an understanding of the data model is a prerequisite to understanding SQL++.</p>
+<p>In what follows, we detail the features of the SQL++ language in a grammar-guided manner. We list and briefly explain each of the productions in the SQL++ grammar, offering examples (and results) for clarity.</p>
+<!-- ! Licensed to the Apache Software Foundation (ASF) under one
+ ! or more contributor license agreements. See the NOTICE file
+ ! distributed with this work for additional information
+ ! regarding copyright ownership. The ASF licenses this file
+ ! to you under the Apache License, Version 2.0 (the
+ ! "License"); you may not use this file except in compliance
+ ! with the License. You may obtain a copy of the License at
+ !
+ ! http://www.apache.org/licenses/LICENSE-2.0
+ !
+ ! Unless required by applicable law or agreed to in writing,
+ ! software distributed under the License is distributed on an
+ ! "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ ! KIND, either express or implied. See the License for the
+ ! specific language governing permissions and limitations
+ ! under the License.
+ ! -->
+<h1><a name="Expressions" id="Expressions">2. Expressions</a></h1>
+
+<div class="source">
+<div class="source">
+<pre>Expression ::= OperatorExpression | CaseExpression | QuantifiedExpression
+</pre></div></div>
+<p>SQL++ is a highly composable expression language. Each SQL++ expression returns zero or more data model instances. There are three major kinds of expressions in SQL++. At the topmost level, a SQL++ expression can be an OperatorExpression (similar to a mathematical expression), an ConditionalExpression (to choose between alternative values), or a QuantifiedExpression (which yields a boolean value). Each will be detailed as we explore the full SQL++ grammar.</p>
+<p>Note that in the following text, words enclosed in angle brackets denote keywords that are not case-sensitive.</p></div>
+<div class="section">
+<h2><a name="Operator_expressions" id="Operator_expressions">Operator expressions</a></h2>
+<p>Operators perform a specific operation on the input values or expressions. The syntax of an operator expression is as follows:</p>
+
+<div class="source">
+<div class="source">
+<pre>OperatorExpression ::= PathExpression
+ | Operator OperatorExpression
+ | OperatorExpression Operator (OperatorExpression)?
+ | OperatorExpression <BETWEEN> OperatorExpression <AND> OperatorExpression
+</pre></div></div>
+<p>SQL++ provides a full set of operators that you can use within its statements. Here are the categories of operators:</p>
+
+<ul>
+
+<li><a href="#Arithmetic_operators">Arithmetic operators</a>, to perform basic mathematical operations;</li>
+
+<li><a href="#Collection_operators">Collection operators</a>, to evaluate expressions on collections or objects;</li>
+
+<li><a href="#Comparison_operators">Comparison operators</a>, to compare two expressions;</li>
+
+<li><a href="#Logical_operators">Logical Operators</a>, to combine operators using Boolean logic.</li>
+</ul>
+<p>The following table summarizes the precedence order (from higher to lower) of the major unary and binary operators:</p>
+
+<table border="0" class="table table-striped">
+ <thead>
+
+<tr class="a">
+
+<th>Operator </th>
+
+<th>Operation </th>
+ </tr>
+ </thead>
+ <tbody>
+
+<tr class="b">
+
+<td>EXISTS, NOT EXISTS </td>
+
+<td>collection emptiness testing </td>
+ </tr>
+
+<tr class="a">
+
+<td>^ </td>
+
+<td>exponentiation </td>
+ </tr>
+
+<tr class="b">
+
+<td>*, /, % </td>
+
+<td>multiplication, division, modulo </td>
+ </tr>
+
+<tr class="a">
+
+<td>+, - </td>
+
+<td>addition, subtraction </td>
+ </tr>
+
+<tr class="b">
+
+<td>|| </td>
+
+<td>string concatenation </td>
+ </tr>
+
+<tr class="a">
+
+<td>IS NULL, IS NOT NULL, IS MISSING, IS NOT MISSING, <br />IS UNKNOWN, IS NOT UNKNOWN</td>
+
+<td>unknown value comparison </td>
+ </tr>
+
+<tr class="b">
+
+<td>BETWEEN, NOT BETWEEN </td>
+
+<td>range comparison (inclusive on both sides) </td>
+ </tr>
+
+<tr class="a">
+
+<td>=, !=, <, >, <=, >=, LIKE, NOT LIKE, IN, NOT IN </td>
+
+<td>comparison </td>
+ </tr>
+
+<tr class="b">
+
+<td>NOT </td>
+
+<td>logical negation </td>
+ </tr>
+
+<tr class="a">
+
+<td>AND </td>
+
+<td>conjunction </td>
+ </tr>
+
+<tr class="b">
+
+<td>OR </td>
+
+<td>disjunction </td>
+ </tr>
+ </tbody>
+</table>
+<p>In general, if any operand evaluates to a <tt>MISSING</tt> value, the enclosing operator will return <tt>MISSING</tt>; if none of operands evaluates to a <tt>MISSING</tt> value but there is an operand evaluates to a <tt>NULL</tt> value, the encolosing operator will return <tt>NULL</tt>. However, there are a few exceptions listed in <a href="#Comparison_operators">comparison operators</a> and <a href="#Logical_operators">logical operators</a>.</p>
+<div class="section">
+<h3><a name="Arithmetic_operators" id="Arithmetic_operators">Arithmetic operators</a></h3>
+<p>Arithemtic operators are used to exponentiate, add, subtract, multiply, and divide numeric values, or concatenate string values.</p>
+
+<table border="0" class="table table-striped">
+ <thead>
+
+<tr class="a">
+
+<th>Operator </th>
+
+<th>Purpose </th>
+
+<th>Example </th>
+ </tr>
+ </thead>
+ <tbody>
+
+<tr class="b">
+
+<td>+, - </td>
+
+<td>As unary operators, they denote a <br />positive or negative expression </td>
+
+<td>SELECT VALUE -1; </td>
+ </tr>
+
+<tr class="a">
+
+<td>+, - </td>
+
+<td>As binary operators, they add or subtract </td>
+
+<td>SELECT VALUE 1 + 2; </td>
+ </tr>
+
+<tr class="b">
+
+<td>*, / </td>
+
+<td>Multiply, divide </td>
+
+<td>SELECT VALUE 4 / 2.0; </td>
+ </tr>
+
+<tr class="a">
+
+<td>^ </td>
+
+<td>Exponentiation </td>
+
+<td>SELECT VALUE 2^3; </td>
+ </tr>
+
+<tr class="b">
+
+<td>|| </td>
+
+<td>String concatenation </td>
+
+<td>SELECT VALUE “ab”||“c”||“d”; </td>
+ </tr>
+ </tbody>
+</table></div>
+<div class="section">
+<h3><a name="Collection_operators" id="Collection_operators">Collection operators</a></h3>
+<p>Collection operators are used for membership tests (IN, NOT IN) or empty collection tests (EXISTS, NOT EXISTS).</p>
+
+<table border="0" class="table table-striped">
+ <thead>
+
+<tr class="a">
+
+<th>Operator </th>
+
+<th>Purpose </th>
+
+<th>Example </th>
+ </tr>
+ </thead>
+ <tbody>
+
+<tr class="b">
+
+<td>IN </td>
+
+<td>Membership test </td>
+
+<td>SELECT * FROM ChirpMessages cm <br />WHERE cm.user.lang IN [“en”, “de”]; </td>
+ </tr>
+
+<tr class="a">
+
+<td>NOT IN </td>
+
+<td>Non-membership test </td>
+
+<td>SELECT * FROM ChirpMessages cm <br />WHERE cm.user.lang NOT IN [“en”]; </td>
+ </tr>
+
+<tr class="b">
+
+<td>EXISTS </td>
+
+<td>Check whether a collection is not empty </td>
+
+<td>SELECT * FROM ChirpMessages cm <br />WHERE EXISTS cm.referredTopics; </td>
+ </tr>
+
+<tr class="a">
+
+<td>NOT EXISTS </td>
+
+<td>Check whether a collection is empty </td>
+
+<td>SELECT * FROM ChirpMessages cm <br />WHERE NOT EXISTS cm.referredTopics; </td>
+ </tr>
+ </tbody>
+</table></div>
+<div class="section">
+<h3><a name="Comparison_operators" id="Comparison_operators">Comparison operators</a></h3>
+<p>Comparison operators are used to compare values. The comparison operators fall into one of two sub-categories: missing value comparisons and regular value comparisons. SQL++ (and JSON) has two ways of representing missing information in a object - the presence of the field with a NULL for its value (as in SQL), and the absence of the field (which JSON permits). For example, the first of the following objects represents Jack, whose friend is Jill. In the other examples, Jake is friendless a la SQL, with a friend field that is NULL, while Joe is friendless in a more natural (for JSON) way, i.e., by not having a friend field.</p>
+<div class="section">
+<div class="section">
+<h5><a name="Examples"></a>Examples</h5>
+<p>{“name”: “Jack”, “friend”: “Jill”}</p>
+<p>{“name”: “Jake”, “friend”: NULL}</p>
+<p>{“name”: “Joe”}</p>
+<p>The following table enumerates all of SQL++’s comparison operators.</p>
+
+<table border="0" class="table table-striped">
+ <thead>
+
+<tr class="a">
+
+<th>Operator </th>
+
+<th>Purpose </th>
+
+<th>Example </th>
+ </tr>
+ </thead>
+ <tbody>
+
+<tr class="b">
+
+<td>IS NULL </td>
+
+<td>Test if a value is NULL </td>
+
+<td>SELECT * FROM ChirpMessages cm <br />WHERE cm.user.name IS NULL; </td>
+ </tr>
+
+<tr class="a">
+
+<td>IS NOT NULL </td>
+
+<td>Test if a value is not NULL </td>
+
+<td>SELECT * FROM ChirpMessages cm <br />WHERE cm.user.name IS NOT NULL; </td>
+ </tr>
+
+<tr class="b">
+
+<td>IS MISSING </td>
+
+<td>Test if a value is MISSING </td>
+
+<td>SELECT * FROM ChirpMessages cm <br />WHERE cm.user.name IS MISSING; </td>
+ </tr>
+
+<tr class="a">
+
+<td>IS NOT MISSING </td>
+
+<td>Test if a value is not MISSING </td>
+
+<td>SELECT * FROM ChirpMessages cm <br />WHERE cm.user.name IS NOT MISSING;</td>
+ </tr>
+
+<tr class="b">
+
+<td>IS UNKNOWN </td>
+
+<td>Test if a value is NULL or MISSING </td>
+
+<td>SELECT * FROM ChirpMessages cm <br />WHERE cm.user.name IS UNKNOWN; </td>
+ </tr>
+
+<tr class="a">
+
+<td>IS NOT UNKNOWN </td>
+
+<td>Test if a value is neither NULL nor MISSING </td>
+
+<td>SELECT * FROM ChirpMessages cm <br />WHERE cm.user.name IS NOT UNKNOWN;</td>
+ </tr>
+
+<tr class="b">
+
+<td>BETWEEN </td>
+
+<td>Test if a value is between a start value and <br />a end value. The comparison is inclusive <br />to both start and end values. </td>
+
+<td>SELECT * FROM ChirpMessages cm <br />WHERE cm.chirpId BETWEEN 10 AND 20;</td>
+ </tr>
+
+<tr class="a">
+
+<td>= </td>
+
+<td>Equality test </td>
+
+<td>SELECT * FROM ChirpMessages cm <br />WHERE cm.chirpId=10; </td>
+ </tr>
+
+<tr class="b">
+
+<td>!= </td>
+
+<td>Inequality test </td>
+
+<td>SELECT * FROM ChirpMessages cm <br />WHERE cm.chirpId!=10;</td>
+ </tr>
+
+<tr class="a">
+
+<td>< </td>
+
+<td>Less than </td>
+
+<td>SELECT * FROM ChirpMessages cm <br />WHERE cm.chirpId<10; </td>
+ </tr>
+
+<tr class="b">
+
+<td>> </td>
+
+<td>Greater than </td>
+
+<td>SELECT * FROM ChirpMessages cm <br />WHERE cm.chirpId>10; </td>
+ </tr>
+
+<tr class="a">
+
+<td><= </td>
+
+<td>Less than or equal to </td>
+
+<td>SELECT * FROM ChirpMessages cm <br />WHERE cm.chirpId<=10; </td>
+ </tr>
+
+<tr class="b">
+
+<td>>= </td>
+
+<td>Greater than or equal to </td>
+
+<td>SELECT * FROM ChirpMessages cm <br />WHERE cm.chirpId>=10; </td>
+ </tr>
+
+<tr class="a">
+
+<td>LIKE </td>
+
+<td>Test if the left side matches a<br /> pattern defined on the right<br /> side; in the pattern, “%” matches <br />any string while “_” matches <br /> any character. </td>
+
+<td>SELECT * FROM ChirpMessages cm <br />WHERE cm.user.name LIKE “%Giesen%”;</td>
+ </tr>
+
+<tr class="b">
+
+<td>NOT LIKE </td>
+
+<td>Test if the left side does not <br />match a pattern defined on the right<br /> side; in the pattern, “%” matches <br />any string while “_” matches <br /> any character. </td>
+
+<td>SELECT * FROM ChirpMessages cm <br />WHERE cm.user.name NOT LIKE “%Giesen%”;</td>
+ </tr>
+ </tbody>
+</table>
+<p>The following table summarizes how the missing value comparison operators work.</p>
+
+<table border="0" class="table table-striped">
+ <thead>
+
+<tr class="a">
+
+<th>Operator </th>
+
+<th>Non-NULL/Non-MISSING value </th>
+
+<th>NULL </th>
+
+<th>MISSING </th>
+ </tr>
+ </thead>
+ <tbody>
+
+<tr class="b">
+
+<td>IS NULL </td>
+
+<td>FALSE </td>
+
+<td>TRUE </td>
+
+<td>MISSING </td>
+ </tr>
+
+<tr class="a">
+
+<td>IS NOT NULL </td>
+
+<td>TRUE </td>
+
+<td>FALSE </td>
+
+<td>MISSING </td>
+ </tr>
+
+<tr class="b">
+
+<td>IS MISSING </td>
+
+<td>FALSE </td>
+
+<td>FALSE </td>
+
+<td>TRUE </td>
+ </tr>
+
+<tr class="a">
+
+<td>IS NOT MISSING </td>
+
+<td>TRUE </td>
+
+<td>TRUE </td>
+
+<td>FALSE </td>
+ </tr>
+
+<tr class="b">
+
+<td>IS UNKNOWN </td>
+
+<td>FALSE </td>
+
+<td>TRUE </td>
+
+<td>TRUE </td>
+ </tr>
+
+<tr class="a">
+
+<td>IS NOT UNKNOWN </td>
+
+<td>TRUE </td>
+
+<td>FALSE </td>
+
+<td>FALSE</td>
+ </tr>
+ </tbody>
+</table></div></div></div>
+<div class="section">
+<h3><a name="Logical_operators" id="Logical_operators">Logical operators</a></h3>
+<p>Logical operators perform logical <tt>NOT</tt>, <tt>AND</tt>, and <tt>OR</tt> operations over Boolean values (<tt>TRUE</tt> and <tt>FALSE</tt>) plus <tt>NULL</tt> and <tt>MISSING</tt>.</p>
+
+<table border="0" class="table table-striped">
+ <thead>
+
+<tr class="a">
+
+<th>Operator </th>
+
+<th>Purpose </th>
+
+<th>Example </th>
+ </tr>
+ </thead>
+ <tbody>
+
+<tr class="b">
+
+<td>NOT </td>
+
+<td>Returns true if the following condition is false, otherwise returns false </td>
+
+<td>SELECT VALUE NOT TRUE; </td>
+ </tr>
+
+<tr class="a">
+
+<td>AND </td>
+
+<td>Returns true if both branches are true, otherwise returns false </td>
+
+<td>SELECT VALUE TRUE AND FALSE; </td>
+ </tr>
+
+<tr class="b">
+
+<td>OR </td>
+
+<td>Returns true if one branch is true, otherwise returns false </td>
+
+<td>SELECT VALUE FALSE OR FALSE; </td>
+ </tr>
+ </tbody>
+</table>
+<p>The following table is the truth table for <tt>AND</tt> and <tt>OR</tt>.</p>
+
+<table border="0" class="table table-striped">
+ <thead>
+
+<tr class="a">
+
+<th>A </th>
+
+<th>B </th>
+
+<th>A AND B </th>
+
+<th>A OR B </th>
+ </tr>
+ </thead>
+ <tbody>
+
+<tr class="b">
+
+<td>TRUE </td>
+
+<td>TRUE </td>
+
+<td>TRUE </td>
+
+<td>TRUE </td>
+ </tr>
+
+<tr class="a">
+
+<td>TRUE </td>
+
+<td>FALSE </td>
+
+<td>FALSE </td>
+
+<td>TRUE </td>
+ </tr>
+
+<tr class="b">
+
+<td>TRUE </td>
+
+<td>NULL </td>
+
+<td>NULL </td>
+
+<td>TRUE </td>
+ </tr>
+
+<tr class="a">
+
+<td>TRUE </td>
+
+<td>MISSING </td>
+
+<td>MISSING </td>
+
+<td>TRUE </td>
+ </tr>
+
+<tr class="b">
+
+<td>FALSE </td>
+
+<td>FALSE </td>
+
+<td>FALSE </td>
+
+<td>FALSE </td>
+ </tr>
+
+<tr class="a">
+
+<td>FALSE </td>
+
+<td>NULL </td>
+
+<td>FALSE </td>
+
+<td>NULL </td>
+ </tr>
+
+<tr class="b">
+
+<td>FALSE </td>
+
+<td>MISSING </td>
+
+<td>FALSE </td>
+
+<td>MISSING </td>
+ </tr>
+
+<tr class="a">
+
+<td>NULL </td>
+
+<td>NULL </td>
+
+<td>NULL </td>
+
+<td>NULL </td>
+ </tr>
+
+<tr class="b">
+
+<td>NULL </td>
+
+<td>MISSING </td>
+
+<td>MISSING </td>
+
+<td>NULL </td>
+ </tr>
+
+<tr class="a">
+
+<td>MISSING </td>
+
+<td>MISSING </td>
+
+<td>MISSING </td>
+
+<td>MISSING </td>
+ </tr>
+ </tbody>
+</table>
+<p>The following table demonstrates the results of <tt>NOT</tt> on all possible inputs.</p>
+
+<table border="0" class="table table-striped">
+ <thead>
+
+<tr class="a">
+
+<th>A </th>
+
+<th>NOT A </th>
+ </tr>
+ </thead>
+ <tbody>
+
+<tr class="b">
+
+<td>TRUE </td>
+
+<td>FALSE </td>
+ </tr>
+
+<tr class="a">
+
+<td>FALSE </td>
+
+<td>TRUE </td>
+ </tr>
+
+<tr class="b">
+
+<td>NULL </td>
+
+<td>NULL </td>
+ </tr>
+
+<tr class="a">
+
+<td>MISSING </td>
+
+<td>MISSING </td>
+ </tr>
+ </tbody>
+</table></div></div>
+<div class="section">
+<h2><a name="Case_expressions" id="Case_expressions">Case expressions</a></h2>
+
+<div class="source">
+<div class="source">
+<pre>CaseExpression ::= SimpleCaseExpression | SearchedCaseExpression
+SimpleCaseExpression ::= <CASE> Expression ( <WHEN> Expression <THEN> Expression )+ ( <ELSE> Expression )? <END>
+SearchedCaseExpression ::= <CASE> ( <WHEN> Expression <THEN> Expression )+ ( <ELSE> Expression )? <END>
+</pre></div></div>
+<p>In a simple <tt>CASE</tt> expression, the query evaluator searches for the first <tt>WHEN</tt> … <tt>THEN</tt> pair in which the <tt>WHEN</tt> expression is equal to the expression following <tt>CASE</tt> and returns the expression following <tt>THEN</tt>. If none of the <tt>WHEN</tt> … <tt>THEN</tt> pairs meet this condition, and an <tt>ELSE</tt> branch exists, it returns the <tt>ELSE</tt> expression. Otherwise, <tt>NULL</tt> is returned.</p>
+<p>In a searched CASE expression, the query evaluator searches from left to right until it finds a <tt>WHEN</tt> expression that is evaluated to <tt>TRUE</tt>, and then returns its corresponding <tt>THEN</tt> expression. If no condition is found to be <tt>TRUE</tt>, and an <tt>ELSE</tt> branch exists, it returns the <tt>ELSE</tt> expression. Otherwise, it returns <tt>NULL</tt>.</p>
+<p>The following example illustrates the form of a case expression.</p>
+<div class="section">
+<div class="section">
+<div class="section">
+<h5><a name="Example"></a>Example</h5>
+
+<div class="source">
+<div class="source">
+<pre>CASE (2 < 3) WHEN true THEN "yes" ELSE "no" END
+</pre></div></div></div></div></div></div>
+<div class="section">
+<h2><a name="Quantified_expressions" id="Quantified_expressions">Quantified expressions</a></h2>
+
+<div class="source">
+<div class="source">
+<pre>QuantifiedExpression ::= ( (<ANY>|<SOME>) | <EVERY> ) Variable <IN> Expression ( "," Variable "in" Expression )*
+ <SATISFIES> Expression (<END>)?
+</pre></div></div>
+<p>Quantified expressions are used for expressing existential or universal predicates involving the elements of a collection.</p>
+<p>The following pair of examples illustrate the use of a quantified expression to test that every (or some) element in the set [1, 2, 3] of integers is less than three. The first example yields <tt>FALSE</tt> and second example yields <tt>TRUE</tt>.</p>
+<p>It is useful to note that if the set were instead the empty set, the first expression would yield <tt>TRUE</tt> (“every” value in an empty set satisfies the condition) while the second expression would yield <tt>FALSE</tt> (since there isn’t “some” value, as there are no values in the set, that satisfies the condition).</p>
+<p>A quantified expression will return a <tt>NULL</tt> (or <tt>MISSING</tt>) if the first expression in it evaluates to <tt>NULL</tt> (or <tt>MISSING</tt>). A type error will be raised if the first expression in a quantified expression does not return a collection.</p>
+<div class="section">
+<div class="section">
+<div class="section">
+<h5><a name="Examples"></a>Examples</h5>
+
+<div class="source">
+<div class="source">
+<pre>EVERY x IN [ 1, 2, 3 ] SATISFIES x < 3
+SOME x IN [ 1, 2, 3 ] SATISFIES x < 3
+</pre></div></div></div></div></div></div>
+<div class="section">
+<h2><a name="Path_expressions" id="Path_expressions">Path expressions</a></h2>
+
+<div class="source">
+<div class="source">
+<pre>PathExpression ::= PrimaryExpression ( Field | Index )*
+Field ::= "." Identifier
+Index ::= "[" ( Expression | "?" ) "]"
+</pre></div></div>
+<p>Components of complex types in the data model are accessed via path expressions. Path access can be applied to the result of a SQL++ expression that yields an instance of a complex type, e.g., a object or array instance. For objects, path access is based on field names. For arrays, path access is based on (zero-based) array-style indexing. SQL++ also supports an “I’m feeling lucky” style index accessor, [?], for selecting an arbitrary element from an array. Attempts to access non-existent fields or out-of-bound array elements produce the special value <tt>MISSING</tt>. Type errors will be raised for inappropriate use of a path expression, such as applying a field accessor to a numeric value.</p>
+<p>The following examples illustrate field access for a object, index-based element access for an array, and also a composition thereof.</p>
+<div class="section">
+<div class="section">
+<div class="section">
+<h5><a name="Examples"></a>Examples</h5>
+
+<div class="source">
+<div class="source">
+<pre>({"name": "MyABCs", "array": [ "a", "b", "c"]}).array
+
+(["a", "b", "c"])[2]
+
+({"name": "MyABCs", "array": [ "a", "b", "c"]}).array[2]
+</pre></div></div></div></div></div></div>
+<div class="section">
+<h2><a name="Primary_Expressions"></a><a name="Primary_expressions" id="Primary_expressions">Primary Expressions</a></h2>
+
+<div class="source">
+<div class="source">
+<pre>PrimaryExpr ::= Literal
+ | VariableReference
+ | ParenthesizedExpression
+ | FunctionCallExpression
+ | Constructor
+</pre></div></div>
+<p>The most basic building block for any SQL++ expression is PrimaryExpression. This can be a simple literal (constant) value, a reference to a query variable that is in scope, a parenthesized expression, a function call, or a newly constructed instance of the data model (such as a newly constructed object, array, or multiset of data model instances).</p>
+<div class="section">
+<h3><a name="Literals" id="Literals">Literals</a></h3>
+
+<div class="source">
+<div class="source">
+<pre>Literal ::= StringLiteral
+ | IntegerLiteral
+ | FloatLiteral
+ | DoubleLiteral
+ | <NULL>
+ | <MISSING>
+ | <TRUE>
+ | <FALSE>
+StringLiteral ::= "\"" (
+ <EscapeQuot>
+ | <EscapeBslash>
+ | <EscapeSlash>
+ | <EscapeBspace>
+ | <EscapeFormf>
+ | <EscapeNl>
+ | <EscapeCr>
+ | <EscapeTab>
+ | ~["\"","\\"])*
+ "\""
+ | "\'"(
+ <EscapeApos>
+ | <EscapeBslash>
+ | <EscapeSlash>
+ | <EscapeBspace>
+ | <EscapeFormf>
+ | <EscapeNl>
+ | <EscapeCr>
+ | <EscapeTab>
+ | ~["\'","\\"])*
+ "\'"
+<ESCAPE_Apos> ::= "\\\'"
+<ESCAPE_Quot> ::= "\\\""
+<EscapeBslash> ::= "\\\\"
+<EscapeSlash> ::= "\\/"
+<EscapeBspace> ::= "\\b"
+<EscapeFormf> ::= "\\f"
+<EscapeNl> ::= "\\n"
+<EscapeCr> ::= "\\r"
+<EscapeTab> ::= "\\t"
+
+IntegerLiteral ::= <DIGITS>
+<DIGITS> ::= ["0" - "9"]+
+FloatLiteral ::= <DIGITS> ( "f" | "F" )
+ | <DIGITS> ( "." <DIGITS> ( "f" | "F" ) )?
+ | "." <DIGITS> ( "f" | "F" )
+DoubleLiteral ::= <DIGITS> "." <DIGITS>
+ | "." <DIGITS>
+</pre></div></div>
+<p>Literals (constants) in SQL++ can be strings, integers, floating point values, double values, boolean constants, or special constant values like <tt>NULL</tt> and <tt>MISSING</tt>. The <tt>NULL</tt> value is like a <tt>NULL</tt> in SQL; it is used to represent an unknown field value. The specialy value <tt>MISSING</tt> is only meaningful in the context of SQL++ field accesses; it occurs when the accessed field simply does not exist at all in a object being accessed.</p>
+<p>The following are some simple examples of SQL++ literals.</p>
+<div class="section">
+<div class="section">
+<h5><a name="Examples"></a>Examples</h5>
+
+<div class="source">
+<div class="source">
+<pre>'a string'
+"test string"
+42
+</pre></div></div>
+<p>Different from standard SQL, double quotes play the same role as single quotes and may be used for string literals in SQL++.</p></div></div></div>
+<div class="section">
+<h3><a name="Variable_References"></a><a name="Variable_references" id="Variable_references">Variable References</a></h3>
+
+<div class="source">
+<div class="source">
+<pre>VariableReference ::= <IDENTIFIER>|<DelimitedIdentifier>
+<IDENTIFIER> ::= <LETTER> (<LETTER> | <DIGIT> | "_" | "$")*
+<LETTER> ::= ["A" - "Z", "a" - "z"]
+DelimitedIdentifier ::= "`" (<EscapeQuot>
+ | <EscapeBslash>
+ | <EscapeSlash>
+ | <EscapeBspace>
+ | <EscapeFormf>
+ | <EscapeNl>
+ | <EscapeCr>
+ | <EscapeTab>
+ | ~["`","\\"])*
+ "`"
+</pre></div></div>
+<p>A variable in SQL++ can be bound to any legal data model value. A variable reference refers to the value to which an in-scope variable is bound. (E.g., a variable binding may originate from one of the <tt>FROM</tt>, <tt>WITH</tt> or <tt>LET</tt> clauses of a <tt>SELECT</tt> statement or from an input parameter in the context of a function body.) Backticks, e.g., `id`, are used for delimited identifiers. Delimiting is needed when a variable’s desired name clashes with a SQL++ keyword or includes characters not allowed in regular identifiers.</p>
+<div class="section">
+<div class="section">
+<h5><a name="Examples"></a>Examples</h5>
+
+<div class="source">
+<div class="source">
+<pre>tweet
+id
+`SELECT`
+`my-function`
+</pre></div></div></div></div></div>
+<div class="section">
+<h3><a name="Parenthesized_expressions" id="Parenthesized_expressions">Parenthesized expressions</a></h3>
+
+<div class="source">
+<div class="source">
+<pre>ParenthesizedExpression ::= "(" Expression ")" | Subquery
+</pre></div></div>
+<p>An expression can be parenthesized to control the precedence order or otherwise clarify a query. In SQL++, for composability, a subquery is also an parenthesized expression.</p>
+<p>The following expression evaluates to the value 2.</p>
+<div class="section">
+<div class="section">
+<h5><a name="Example"></a>Example</h5>
+
+<div class="source">
+<div class="source">
+<pre>( 1 + 1 )
+</pre></div></div></div></div></div>
+<div class="section">
+<h3><a name="Function_call_expressions" id="Function_call_expressions">Function call expressions</a></h3>
+
+<div class="source">
+<div class="source">
+<pre>FunctionCallExpression ::= FunctionName "(" ( Expression ( "," Expression )* )? ")"
+</pre></div></div>
+<p>Functions are included in SQL++, like most languages, as a way to package useful functionality or to componentize complicated or reusable SQL++ computations. A function call is a legal SQL++ query expression that represents the value resulting from the evaluation of its body expression with the given parameter bindings; the parameter value bindings can themselves be any SQL++ expressions.</p>
+<p>The following example is a (built-in) function call expression whose value is 8.</p>
+<div class="section">
+<div class="section">
+<h5><a name="Example"></a>Example</h5>
+
+<div class="source">
+<div class="source">
+<pre>length('a string')
+</pre></div></div></div></div></div>
+<div class="section">
+<h3><a name="Constructors" id="Constructors">Constructors</a></h3>
+
+<div class="source">
+<div class="source">
+<pre>Constructor ::= ArrayConstructor | MultisetConstructor | ObjectConstructor
+ArrayConstructor ::= "[" ( Expression ( "," Expression )* )? "]"
+MultisetConstructor ::= "{{" ( Expression ( "," Expression )* )? "}}"
+ObjectConstructor ::= "{" ( FieldBinding ( "," FieldBinding )* )? "}"
+FieldBinding ::= Expression ":" Expression
+</pre></div></div>
+<p>A major feature of SQL++ is its ability to construct new data model instances. This is accomplished using its constructors for each of the model’s complex object structures, namely arrays, multisets, and objects. Arrays are like JSON arrays, while multisets have bag semantics. Objects are built from fields that are field-name/field-value pairs, again like JSON.</p>
+<p>The following examples illustrate how to construct a new array with 4 items, a new object with 2 fields, and a new multiset with 5 items, respectively. Array elements or multiset elements can be homogeneous (as in the first example), which is the common case, or they may be heterogeneous (as in the third example). The data values and field name values used to construct arrays, multisets, and objects in constructors are all simply SQL++ expressions. Thus, the collection elements, field names, and field values used in constructors can be simple literals or they can come from query variable references or even arbitrarily complex SQL++ expressions (subqueries). Type errors will be raised if the field names in a record must be strings, and duplicate field errors will be raised if they are not distinct.</p>
+<div class="section">
+<div class="section">
+<h5><a name="Examples"></a>Examples</h5>
+
+<div class="source">
+<div class="source">
+<pre>[ 'a', 'b', 'c', 'c' ]
+
+{
+ 'project name': 'Hyracks',
+ 'project members': [ 'vinayakb', 'dtabass', 'chenli', 'tsotras', 'tillw' ]
+}
+
+{{ 42, "forty-two!", { "rank": "Captain", "name": "America" }, 3.14159, 42 }}
+</pre></div></div>
+<!-- ! Licensed to the Apache Software Foundation (ASF) under one
+ ! or more contributor license agreements. See the NOTICE file
+ ! distributed with this work for additional information
+ ! regarding copyright ownership. The ASF licenses this file
+ ! to you under the Apache License, Version 2.0 (the
+ ! "License"); you may not use this file except in compliance
+ ! with the License. You may obtain a copy of the License at
+ !
+ ! http://www.apache.org/licenses/LICENSE-2.0
+ !
+ ! Unless required by applicable law or agreed to in writing,
+ ! software distributed under the License is distributed on an
+ ! "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ ! KIND, either express or implied. See the License for the
+ ! specific language governing permissions and limitations
+ ! under the License.
+ ! -->
+<h1><a name="Queries" id="Queries">3. Queries</a></h1>
+<p>A SQL++ query can be any legal SQL++ expression or <tt>SELECT</tt> statement. A SQL++ query always ends with a semicolon.</p>
+
+<div class="source">
+<div class="source">
+<pre>Query ::= (Expression | SelectStatement) ";"
+</pre></div></div></div></div></div></div>
+<div class="section">
+<h2><a name="SELECT_statements" id="SELECT_statements">SELECT statements</a></h2>
+<p>The following shows the (rich) grammar for the <tt>SELECT</tt> statement in SQL++.</p>
+
+<div class="source">
+<div class="source">
+<pre>SelectStatement ::= ( WithClause )?
+ SelectSetOperation (OrderbyClause )? ( LimitClause )?
+SelectSetOperation ::= SelectBlock (<UNION> <ALL> ( SelectBlock | Subquery ) )*
+Subquery ::= "(" SelectStatement ")"
+
+SelectBlock ::= SelectClause
+ ( FromClause ( LetClause )?)?
+ ( WhereClause )?
+ ( GroupbyClause ( LetClause )? ( HavingClause )? )?
+ |
+ FromClause ( LetClause )?
+ ( WhereClause )?
+ ( GroupbyClause ( LetClause )? ( HavingClause )? )?
+ SelectClause
+
+SelectClause ::= <SELECT> ( <ALL> | <DISTINCT> )? ( SelectRegular | SelectValue )
+SelectRegular ::= Projection ( "," Projection )*
+SelectValue ::= ( <VALUE> | <ELEMENT> | <RAW> ) Expression
+Projection ::= ( Expression ( <AS> )? Identifier | "*" )
+
+FromClause ::= <FROM> FromTerm ( "," FromTerm )*
+FromTerm ::= Expression (( <AS> )? Variable)?
+ ( ( JoinType )? ( JoinClause | UnnestClause ) )*
+
+JoinClause ::= <JOIN> Expression (( <AS> )? Variable)? <ON> Expression
+UnnestClause ::= ( <UNNEST> | <CORRELATE> | <FLATTEN> ) Expression
+ ( <AS> )? Variable ( <AT> Variable )?
+JoinType ::= ( <INNER> | <LEFT> ( <OUTER> )? )
+
+WithClause ::= <WITH> WithElement ( "," WithElement )*
+LetClause ::= (<LET> | <LETTING>) LetElement ( "," LetElement )*
+LetElement ::= Variable "=" Expression
+WithElement ::= Variable <AS> Expression
+
+WhereClause ::= <WHERE> Expression
+
+GroupbyClause ::= <GROUP> <BY> ( Expression ( (<AS>)? Variable )? ( "," Expression ( (<AS>)? Variable )? )*
+ ( <GROUP> <AS> Variable
+ ("(" Variable <AS> VariableReference ("," Variable <AS> VariableReference )* ")")?
+ )?
+HavingClause ::= <HAVING> Expression
+
+OrderbyClause ::= <ORDER> <BY> Expression ( <ASC> | <DESC> )? ( "," Expression ( <ASC> | <DESC> )? )*
+LimitClause ::= <LIMIT> Expression ( <OFFSET> Expression )?
+</pre></div></div>
+<p>In this section, we will make use of two stored collections of objects (datasets), <tt>GleambookUsers</tt> and <tt>GleambookMessages</tt>, in a series of running examples to explain <tt>SELECT</tt> queries. The contents of the example collections are as follows:</p>
+<p><tt>GleambookUsers</tt> collection (or, dataset):</p>
+
+<div class="source">
+<div class="source">
+<pre>{"id":1,"alias":"Margarita","name":"MargaritaStoddard","nickname":"Mags","userSince":"2012-08-20T10:10:00","friendIds":[2,3,6,10],"employment":[{"organizationName":"Codetechno","start-date":"2006-08-06"},{"organizationName":"geomedia","start-date":"2010-06-17","end-date":"2010-01-26"}],"gender":"F"}
+{"id":2,"alias":"Isbel","name":"IsbelDull","nickname":"Izzy","userSince":"2011-01-22T10:10:00","friendIds":[1,4],"employment":[{"organizationName":"Hexviafind","startDate":"2010-04-27"}]}
+{"id":3,"alias":"Emory","name":"EmoryUnk","userSince":"2012-07-10T10:10:00","friendIds":[1,5,8,9],"employment":[{"organizationName":"geomedia","startDate":"2010-06-17","endDate":"2010-01-26"}]}
+</pre></div></div>
+<p><tt>GleambookMessages</tt> collection (or, dataset):</p>
+
+<div class="source">
+<div class="source">
+<pre>{"messageId":2,"authorId":1,"inResponseTo":4,"senderLocation":[41.66,80.87],"message":" dislike iphone its touch-screen is horrible"}
+{"messageId":3,"authorId":2,"inResponseTo":4,"senderLocation":[48.09,81.01],"message":" like samsung the plan is amazing"}
+{"messageId":4,"authorId":1,"inResponseTo":2,"senderLocation":[37.73,97.04],"message":" can't stand at&t the network is horrible:("}
+{"messageId":6,"authorId":2,"inResponseTo":1,"senderLocation":[31.5,75.56],"message":" like t-mobile its platform is mind-blowing"}
+{"messageId":8,"authorId":1,"inResponseTo":11,"senderLocation":[40.33,80.87],"message":" like verizon the 3G is awesome:)"}
+{"messageId":10,"authorId":1,"inResponseTo":12,"senderLocation":[42.5,70.01],"message":" can't stand motorola the touch-screen is terrible"}
+{"messageId":11,"authorId":1,"inResponseTo":1,"senderLocation":[38.97,77.49],"message":" can't stand at&t its plan is terrible"}
+</pre></div></div></div>
+<div class="section">
+<h2><a name="SELECT_Clause"></a><a name="Select_clauses" id="Select_clauses">SELECT Clause</a></h2>
+<p>The SQL++ <tt>SELECT</tt> clause always returns a collection value as its result (even if the result is empty or a singleton).</p>
+<div class="section">
+<h3><a name="SELECT_VALUE_Clause"></a><a name="Select_element" id="Select_element">SELECT VALUE Clause</a></h3>
+<p>The <tt>SELECT VALUE</tt> clause in SQL++ returns a collection that contains the results of evaluating the <tt>VALUE</tt> expression, with one evaluation being performed per “binding tuple” (i.e., per <tt>FROM</tt> clause item) satisfying the statement’s selection criteria. For historical reasons SQL++ also allows the keywords <tt>ELEMENT</tt> or <tt>RAW</tt> to be used in place of <tt>VALUE</tt> (not recommended).</p>
+<p>The following example shows a standard-alone <tt>SELECT VALUE</tt>, which wraps a value into an array.</p>
+<div class="section">
+<div class="section">
+<h5><a name="Example"></a>Example</h5>
+
+<div class="source">
+<div class="source">
+<pre>SELECT VALUE 1;
+</pre></div></div>
+<p>This query return:</p>
+
+<div class="source">
+<div class="source">
+<pre>[
+ 1
+]
+</pre></div></div>
+<p>The following example shows a query that selects one user from the GleambookUsers collection.</p></div>
+<div class="section">
+<h5><a name="Example"></a>Example</h5>
+
+<div class="source">
+<div class="source">
+<pre>SELECT VALUE user
+FROM GleambookUsers user
+WHERE user.id = 1;
+</pre></div></div>
+<p>This query returns:</p>
+
+<div class="source">
+<div class="source">
+<pre>[{
+ "userSince": "2012-08-20T10:10:00.000Z",
+ "friendIds": [
+ 2,
+ 3,
+ 6,
+ 10
+ ],
+ "gender": "F",
+ "name": "MargaritaStoddard",
+ "nickname": "Mags",
+ "alias": "Margarita",
+ "id": 1,
+ "employment": [
+ {
+ "organizationName": "Codetechno",
+ "start-date": "2006-08-06"
+ },
+ {
+ "end-date": "2010-01-26",
+ "organizationName": "geomedia",
+ "start-date": "2010-06-17"
+ }
+ ]
+} ]
+</pre></div></div></div></div></div>
+<div class="section">
+<h3><a name="SQL-style_SELECT"></a><a name="SQL_select" id="SQL_select">SQL-style SELECT</a></h3>
+<p>In SQL++, the traditional SQL-style <tt>SELECT</tt> syntax is also supported. This syntax can also be reformulated in a <tt>SELECT VALUE</tt> based manner in SQL++. (E.g., <tt>SELECT expA AS fldA, expB AS fldB</tt> is syntactic sugar for <tt>SELECT VALUE { 'fldA': expA, 'fldB': expB }</tt>.) Unlike in SQL, the result of an SQL++ query does not preserve the order of expressions in the <tt>SELECT</tt> clause.</p>
+<div class="section">
+<div class="section">
+<h5><a name="Example"></a>Example</h5>
+
+<div class="source">
+<div class="source">
+<pre>SELECT user.alias user_alias, user.name user_name
+FROM GleambookUsers user
+WHERE user.id = 1;
+</pre></div></div>
+<p>Returns:</p>
+
+<div class="source">
+<div class="source">
+<pre>[ {
+ "user_name": "MargaritaStoddard",
+ "user_alias": "Margarita"
+} ]
+</pre></div></div></div></div></div>
+<div class="section">
+<h3><a name="SELECT_"></a><a name="Select_star" id="Select_star">SELECT *</a></h3>
+<p>In SQL++, <tt>SELECT *</tt> returns a object with a nested field for each input tuple. Each field has as its field name the name of a binding variable generated by either the <tt>FROM</tt> clause or <tt>GROUP BY</tt> clause in the current enclosing <tt>SELECT</tt> statement, and its field value is the value of that binding variable.</p>
+<div class="section">
+<div class="section">
+<h5><a name="Example"></a>Example</h5>
+
+<div class="source">
+<div class="source">
+<pre>SELECT *
+FROM GleambookUsers user;
+</pre></div></div>
+<p>Since <tt>user</tt> is the only binding variable generated in the <tt>FROM</tt> clause, this query returns:</p>
+
+<div class="source">
+<div class="source">
+<pre>[ {
+ "user": {
+ "userSince": "2012-08-20T10:10:00.000Z",
+ "friendIds": [
+ 2,
+ 3,
+ 6,
+ 10
+ ],
+ "gender": "F",
+ "name": "MargaritaStoddard",
+ "nickname": "Mags",
+ "alias": "Margarita",
+ "id": 1,
+ "employment": [
+ {
+ "organizationName": "Codetechno",
+ "start-date": "2006-08-06"
+ },
+ {
+ "end-date": "2010-01-26",
+ "organizationName": "geomedia",
+ "start-date": "2010-06-17"
+ }
+ ]
+ }
+}, {
+ "user": {
+ "userSince": "2011-01-22T10:10:00.000Z",
+ "friendIds": [
+ 1,
+ 4
+ ],
+ "name": "IsbelDull",
+ "nickname": "Izzy",
+ "alias": "Isbel",
+ "id": 2,
+ "employment": [
+ {
+ "organizationName": "Hexviafind",
+ "startDate": "2010-04-27"
+ }
+ ]
+ }
+}, {
+ "user": {
+ "userSince": "2012-07-10T10:10:00.000Z",
+ "friendIds": [
+ 1,
+ 5,
+ 8,
+ 9
+ ],
+ "name": "EmoryUnk",
+ "alias": "Emory",
+ "id": 3,
+ "employment": [
+ {
+ "organizationName": "geomedia",
+ "endDate": "2010-01-26",
+ "startDate": "2010-06-17"
+ }
+ ]
+ }
+} ]
+</pre></div></div></div>
+<div class="section">
+<h5><a name="Example"></a>Example</h5>
+
+<div class="source">
+<div class="source">
+<pre>SELECT *
+FROM GleambookUsers u, GleambookMessages m
+WHERE m.authorId = u.id and u.id = 2;
+</pre></div></div>
+<p>This query does an inner join that we will discuss in <a href="#Multiple_from_terms">multiple from terms</a>. Since both <tt>u</tt> and <tt>m</tt> are binding variable generated in the <tt>FROM</tt> clause, this query returns:</p>
+
+<div class="source">
+<div class="source">
+<pre>[ {
+ "u": {
+ "userSince": "2011-01-22T10:10:00",
+ "friendIds": [
+ 1,
+ 4
+ ],
+ "name": "IsbelDull",
+ "nickname": "Izzy",
+ "alias": "Isbel",
+ "id": 2,
+ "employment": [
+ {
+ "organizationName": "Hexviafind",
+ "startDate": "2010-04-27"
+ }
+ ]
+ },
+ "m": {
+ "senderLocation": [
+ 31.5,
+ 75.56
+ ],
+ "inResponseTo": 1,
+ "messageId": 6,
+ "authorId": 2,
+ "message": " like t-mobile its platform is mind-blowing"
+ }
+}, {
+ "u": {
+ "userSince": "2011-01-22T10:10:00",
+ "friendIds": [
+ 1,
+ 4
+ ],
+ "name": "IsbelDull",
+ "nickname": "Izzy",
+ "alias": "Isbel",
+ "id": 2,
+ "employment": [
+ {
+ "organizationName": "Hexviafind",
+ "startDate": "2010-04-27"
+ }
+ ]
+ },
+ "m": {
+ "senderLocation": [
+ 48.09,
+ 81.01
+ ],
+ "inResponseTo": 4,
+ "messageId": 3,
+ "authorId": 2,
+ "message": " like samsung the plan is amazing"
+ }
+} ]
+</pre></div></div></div></div></div>
+<div class="section">
+<h3><a name="SELECT_DISTINCT"></a><a name="Select_distinct" id="Select_distinct">SELECT DISTINCT</a></h3>
+<p>SQL++’s <tt>DISTINCT</tt> keyword is used to eliminate duplicate items in results. The following example shows how it works.</p>
+<div class="section">
+<div class="section">
+<h5><a name="Example"></a>Example</h5>
+
+<div class="source">
+<div class="source">
+<pre>SELECT DISTINCT * FROM [1, 2, 2, 3] AS foo;
+</pre></div></div>
+<p>This query returns:</p>
+
+<div class="source">
+<div class="source">
+<pre>[ {
+ "foo": 1
+}, {
+ "foo": 2
+}, {
+ "foo": 3
+} ]
+</pre></div></div></div>
+<div class="section">
+<h5><a name="Example"></a>Example</h5>
+
+<div class="source">
+<div class="source">
+<pre>SELECT DISTINCT VALUE foo FROM [1, 2, 2, 3] AS foo;
+</pre></div></div>
+<p>This version of the query returns:</p>
+
+<div class="source">
+<div class="source">
+<pre>[ 1
+, 2
+, 3
+ ]
+</pre></div></div></div></div></div>
+<div class="section">
+<h3><a name="Unnamed_projections" id="Unnamed_projections">Unnamed projections</a></h3>
+<p>Similar to standard SQL, SQL++ supports unnamed projections (a.k.a, unnamed <tt>SELECT</tt> clause items), for which names are generated. Name generation has three cases:</p>
+
+<ul>
+
+<li>If a projection expression is a variable reference expression, its generated name is the name of the variable.</li>
+
+<li>If a projection expression is a field access expression, its generated name is the last identifier in the expression.</li>
+
+<li>For all other cases, the query processor will generate a unique name.</li>
+</ul>
+<div class="section">
+<div class="section">
+<h5><a name="Example"></a>Example</h5>
+
+<div class="source">
+<div class="source">
+<pre>SELECT substr(user.name, 10), user.alias
+FROM GleambookUsers user
+WHERE user.id = 1;
+</pre></div></div>
+<p>This query outputs:</p>
+
+<div class="source">
+<div class="source">
+<pre>[ {
+ "alias": "Margarita",
+ "$1": "Stoddard"
+} ]
+</pre></div></div>
+<p>In the result, <tt>$1</tt> is the generated name for <tt>substr(user.name, 1)</tt>, while <tt>alias</tt> is the generated name for <tt>user.alias</tt>.</p></div></div></div>
+<div class="section">
+<h3><a name="Abbreviated_Field_Access_Expressions"></a><a name="Abbreviatory_field_access_expressions" id="Abbreviatory_field_access_expressions">Abbreviated Field Access Expressions</a></h3>
+<p>As in standard SQL, SQL++ field access expressions can be abbreviated (not recommended) when there is no ambiguity. In the next example, the variable <tt>user</tt> is the only possible variable reference for fields <tt>id</tt>, <tt>name</tt> and <tt>alias</tt> and thus could be omitted in the query.</p>
+<div class="section">
+<div class="section">
+<h5><a name="Example"></a>Example</h5>
+
+<div class="source">
+<div class="source">
+<pre>SELECT substr(name, 10) AS lname, alias
+FROM GleambookUsers user
+WHERE id = 1;
+</pre></div></div>
+<p>Outputs:</p>
+
+<div class="source">
+<div class="source">
+<pre>[ {
+ "lname": "Stoddard",
+ "alias": "Margarita"
+} ]
+</pre></div></div></div></div></div></div>
+<div class="section">
+<h2><a name="UNNEST_Clause"></a><a name="Unnest_clauses" id="Unnest_clauses">UNNEST Clause</a></h2>
+<p>For each of its input tuples, the <tt>UNNEST</tt> clause flattens a collection-valued expression into individual items, producing multiple tuples, each of which is one of the expression’s original input tuples augmented with a flattened item from its collection.</p>
+<div class="section">
+<h3><a name="Inner_UNNEST"></a><a name="Inner_unnests" id="Inner_unnests">Inner UNNEST</a></h3>
+<p>The following example is a query that retrieves the names of the organizations that a selected user has worked for. It uses the <tt>UNNEST</tt> clause to unnest the nested collection <tt>employment</tt> in the user’s object.</p>
+<div class="section">
+<div class="section">
+<h5><a name="Example"></a>Example</h5>
+
+<div class="source">
+<div class="source">
+<pre>SELECT u.id AS userId, e.organizationName AS orgName
+FROM GleambookUsers u
+UNNEST u.employment e
+WHERE u.id = 1;
+</pre></div></div>
+<p>This query returns:</p>
+
+<div class="source">
+<div class="source">
+<pre>[ {
+ "orgName": "Codetechno",
+ "userId": 1
+}, {
+ "orgName": "geomedia",
+ "userId": 1
+} ]
+</pre></div></div>
+<p>Note that <tt>UNNEST</tt> has SQL’s inner join semantics — that is, if a user has no employment history, no tuple corresponding to that user will be emitted in the result.</p></div></div></div>
+<div class="section">
+<h3><a name="Left_outer_UNNEST"></a><a name="Left_outer_unnests" id="Left_outer_unnests">Left outer UNNEST</a></h3>
+<p>As an alternative, the <tt>LEFT OUTER UNNEST</tt> clause offers SQL’s left outer join semantics. For example, no collection-valued field named <tt>hobbies</tt> exists in the object for the user whose id is 1, but the following query’s result still includes user 1.</p>
+<div class="section">
+<div class="section">
+<h5><a name="Example"></a>Example</h5>
+
+<div class="source">
+<div class="source">
+<pre>SELECT u.id AS userId, h.hobbyName AS hobby
+FROM GleambookUsers u
+LEFT OUTER UNNEST u.hobbies h
+WHERE u.id = 1;
+</pre></div></div>
+<p>Returns:</p>
+
+<div class="source">
+<div class="source">
+<pre>[ {
+ "userId": 1
+} ]
+</pre></div></div>
+<p>Note that if <tt>u.hobbies</tt> is an empty collection or leads to a <tt>MISSING</tt> (as above) or <tt>NULL</tt> value for a given input tuple, there is no corresponding binding value for variable <tt>h</tt> for an input tuple. A <tt>MISSING</tt> value will be generated for <tt>h</tt> so that the input tuple can still be propagated.</p></div></div></div>
+<div class="section">
+<h3><a name="Expressing_joins_using_UNNEST"></a><a name="Expressing_joins_using_unnests" id="Expressing_joins_using_unnests">Expressing joins using UNNEST</a></h3>
+<p>The SQL++ <tt>UNNEST</tt> clause is similar to SQL’s <tt>JOIN</tt> clause except that it allows its right argument to be correlated to its left argument, as in the examples above — i.e., think “correlated cross-product”. The next example shows this via a query that joins two data sets, GleambookUsers and GleambookMessages, returning user/message pairs. The results contain one object per pair, with result objects containing the user’s name and an entire message. The query can be thought of as saying “for each Gleambook user, unnest the <tt>GleambookMessages</tt> collection and filter the output with the condition <tt>message.authorId = user.id</tt>”.</p>
+<div class="section">
+<div class="section">
+<h5><a name="Example"></a>Example</h5>
+
+<div class="source">
+<div class="source">
+<pre>SELECT u.name AS uname, m.message AS message
+FROM GleambookUsers u
+UNNEST GleambookMessages m
+WHERE m.authorId = u.id;
+</pre></div></div>
+<p>This returns:</p>
+
+<div class="source">
+<div class="source">
+<pre>[ {
+ "uname": "MargaritaStoddard",
+ "message": " can't stand at&t its plan is terrible"
+}, {
+ "uname": "MargaritaStoddard",
+ "message": " dislike iphone its touch-screen is horrible"
+}, {
+ "uname": "MargaritaStoddard",
+ "message": " can't stand at&t the network is horrible:("
+}, {
+ "uname": "MargaritaStoddard",
+ "message": " like verizon the 3G is awesome:)"
+}, {
+ "uname": "MargaritaStoddard",
+ "message": " can't stand motorola the touch-screen is terrible"
+}, {
+ "uname": "IsbelDull",
+ "message": " like t-mobile its platform is mind-blowing"
+}, {
+ "uname": "IsbelDull",
+ "message": " like samsung the plan is amazing"
+} ]
+</pre></div></div>
+<p>Similarly, the above query can also be expressed as the <tt>UNNEST</tt>ing of a correlated SQL++ subquery:</p></div>
+<div class="section">
+<h5><a name="Example"></a>Example</h5>
+
+<div class="source">
+<div class="source">
+<pre>SELECT u.name AS uname, m.message AS message
+FROM GleambookUsers u
+UNNEST (
+ SELECT VALUE msg
+ FROM GleambookMessages msg
+ WHERE msg.authorId = u.id
+) AS m;
+</pre></div></div></div></div></div></div>
+<div class="section">
+<h2><a name="FROM_clauses"></a><a name="From_clauses" id="From_clauses">FROM clauses</a></h2>
+<p>A <tt>FROM</tt> clause is used for enumerating (i.e., conceptually iterating over) the contents of collections, as in SQL.</p>
+<div class="section">
+<h3><a name="Binding_expressions" id="Binding_expressions">Binding expressions</a></h3>
+<p>In SQL++, in addition to stored collections, a <tt>FROM</tt> clause can iterate over any intermediate collection returned by a valid SQL++ expression. In the tuple stream generated by a <tt>FROM</tt> clause, the ordering of the input tuples are not guaranteed to be preserved.</p>
+<div class="section">
+<div class="section">
+<h5><a name="Example"></a>Example</h5>
+
+<div class="source">
+<div class="source">
+<pre>SELECT VALUE foo
+FROM [1, 2, 2, 3] AS foo
+WHERE foo > 2;
+</pre></div></div>
+<p>Returns:</p>
+
+<div class="source">
+<div class="source">
+<pre>[
+ 3
+]
+</pre></div></div></div></div></div>
+<div class="section">
+<h3><a name="Multiple_FROM_terms"></a><a name="Multiple_from_terms" id="Multiple_from_terms">Multiple FROM terms</a></h3>
+<p>SQL++ permits correlations among <tt>FROM</tt> terms. Specifically, a <tt>FROM</tt> binding expression can refer to variables defined to its left in the given <tt>FROM</tt> clause. Thus, the first unnesting example above could also be expressed as follows:</p>
+<div class="section">
+<div class="section">
+<h5><a name="Example"></a>Example</h5>
+
+<div class="source">
+<div class="source">
+<pre>SELECT u.id AS userId, e.organizationName AS orgName
+FROM GleambookUsers u, u.employment e
+WHERE u.id = 1;
+</pre></div></div></div></div></div>
+<div class="section">
+<h3><a name="Expressing_joins_using_FROM_terms"></a><a name="Expressing_joins_using_from_terms" id="Expressing_joins_using_from_terms">Expressing joins using FROM terms</a></h3>
+<p>Similarly, the join intentions of the other <tt>UNNEST</tt>-based join examples above could be expressed as:</p>
+<div class="section">
+<div class="section">
+<h5><a name="Example"></a>Example</h5>
+
+<div class="source">
+<div class="source">
+<pre>SELECT u.name AS uname, m.message AS message
+FROM GleambookUsers u, GleambookMessages m
+WHERE m.authorId = u.id;
+</pre></div></div></div>
+<div class="section">
+<h5><a name="Example"></a>Example</h5>
+
+<div class="source">
+<div class="source">
+<pre>SELECT u.name AS uname, m.message AS message
+FROM GleambookUsers u,
+ (
+ SELECT VALUE msg
+ FROM GleambookMessages msg
+ WHERE msg.authorId = u.id
+ ) AS m;
+</pre></div></div>
+<p>Note that the first alternative is one of the SQL-92 approaches to expressing a join.</p></div></div></div>
+<div class="section">
+<h3><a name="Implicit_binding_variables" id="Implicit_binding_variables">Implicit binding variables</a></h3>
+<p>Similar to standard SQL, SQL++ supports implicit <tt>FROM</tt> binding variables (i.e., aliases), for which a binding variable is generated. SQL++ variable generation falls into three cases:</p>
+
+<ul>
+
+<li>If the binding expression is a variable reference expression, the generated variable’s name will be the name of the referenced variable itself.</li>
+
+<li>If the binding expression is a field access expression (or a fully qualified name for a dataset), the generated variable’s name will be the last identifier (or the dataset name) in the expression.</li>
+
+<li>For all other cases, a compilation error will be raised.</li>
+</ul>
+<p>The next two examples show queries that do not provide binding variables in their <tt>FROM</tt> clauses.</p>
+<div class="section">
+<div class="section">
+<h5><a name="Example"></a>Example</h5>
+
+<div class="source">
+<div class="source">
+<pre>SELECT GleambookUsers.name, GleambookMessages.message
+FROM GleambookUsers, GleambookMessages
+WHERE GleambookMessages.authorId = GleambookUsers.id;
+</pre></div></div>
+<p>Returns:</p>
+
+<div class="source">
+<div class="source">
+<pre>[ {
+ "name": "MargaritaStoddard",
+ "message": " like verizon the 3G is awesome:)"
+}, {
+ "name": "MargaritaStoddard",
+ "message": " can't stand motorola the touch-screen is terrible"
+}, {
+ "name": "MargaritaStoddard",
+ "message": " can't stand at&t its plan is terrible"
+}, {
+ "name": "MargaritaStoddard",
+ "message": " dislike iphone its touch-screen is horrible"
+}, {
+ "name": "MargaritaStoddard",
+ "message": " can't stand at&t the network is horrible:("
+}, {
+ "name": "IsbelDull",
+ "message": " like samsung the plan is amazing"
+}, {
+ "name": "IsbelDull",
+ "message": " like t-mobile its platform is mind-blowing"
+} ]
+</pre></div></div></div>
+<div class="section">
+<h5><a name="Example"></a>Example</h5>
+
+<div class="source">
+<div class="source">
+<pre>SELECT GleambookUsers.name, GleambookMessages.message
+FROM GleambookUsers,
+ (
+ SELECT VALUE GleambookMessages
+ FROM GleambookMessages
+ WHERE GleambookMessages.authorId = GleambookUsers.id
+ );
+</pre></div></div>
+<p>Returns:</p>
+
+<div class="source">
+<div class="source">
+<pre>Error: "Syntax error: Need an alias for the enclosed expression:\n(select element GleambookMessages\n from GleambookMessages as GleambookMessages\n where (GleambookMessages.authorId = GleambookUsers.id)\n )",
+ "query_from_user": "use TinySocial;\n\nSELECT GleambookUsers.name, GleambookMessages.message\n FROM GleambookUsers,\n (\n SELECT VALUE GleambookMessages\n FROM GleambookMessages\n WHERE GleambookMessages.authorId = GleambookUsers.id\n );"
+</pre></div></div></div></div></div></div>
+<div class="section">
+<h2><a name="JOIN_clauses"></a><a name="Join_clauses" id="Join_clauses">JOIN clauses</a></h2>
+<p>The join clause in SQL++ supports both inner joins and left outer joins from standard SQL.</p>
+<div class="section">
+<h3><a name="Inner_joins" id="Inner_joins">Inner joins</a></h3>
+<p>Using a <tt>JOIN</tt> clause, the inner join intent from the preceeding examples can also be expressed as follows:</p>
+<div class="section">
+<div class="section">
+<h5><a name="Example"></a>Example</h5>
+
+<div class="source">
+<div class="source">
+<pre>SELECT u.name AS uname, m.message AS message
+FROM GleambookUsers u JOIN GleambookMessages m ON m.authorId = u.id;
+</pre></div></div></div></div></div>
+<div class="section">
+<h3><a name="Left_outer_joins" id="Left_outer_joins">Left outer joins</a></h3>
+<p>SQL++ supports SQL’s notion of left outer join. The following query is an example:</p>
+
+<div class="source">
+<div class="source">
+<pre>SELECT u.name AS uname, m.message AS message
+FROM GleambookUsers u LEFT OUTER JOIN GleambookMessages m ON m.authorId = u.id;
+</pre></div></div>
+<p>Returns:</p>
+
+<div class="source">
+<div class="source">
+<pre>[ {
+ "uname": "MargaritaStoddard",
+ "message": " like verizon the 3G is awesome:)"
+}, {
+ "uname": "MargaritaStoddard",
+ "message": " can't stand motorola the touch-screen is terrible"
+}, {
+ "uname": "MargaritaStoddard",
+ "message": " can't stand at&t its plan is terrible"
+}, {
+ "uname": "MargaritaStoddard",
+ "message": " dislike iphone its touch-screen is horrible"
+}, {
+ "uname": "MargaritaStoddard",
+ "message": " can't stand at&t the network is horrible:("
+}, {
+ "uname": "IsbelDull",
+ "message": " like samsung the plan is amazing"
+}, {
+ "uname": "IsbelDull",
+ "message": " like t-mobile its platform is mind-blowing"
+}, {
+ "uname": "EmoryUnk"
+} ]
+</pre></div></div>
+<p>For non-matching left-side tuples, SQL++ produces <tt>MISSING</tt> values for the right-side binding variables; that is why the last object in the above result doesn’t have a <tt>message</tt> field. Note that this is slightly different from standard SQL, which instead would fill in <tt>NULL</tt> values for the right-side fields. The reason for this difference is that, for non-matches in its join results, SQL++ views fields from the right-side as being “not there” (a.k.a. <tt>MISSING</tt>) instead of as being “there but unknown” (i.e., <tt>NULL</tt>).</p>
+<p>The left-outer join query can also be expressed using <tt>LEFT OUTER UNNEST</tt>:</p>
+
+<div class="source">
+<div class="source">
+<pre>SELECT u.name AS uname, m.message AS message
+FROM GleambookUsers u
+LEFT OUTER UNNEST (
+ SELECT VALUE message
+ FROM GleambookMessages message
+ WHERE message.authorId = u.id
+ ) m;
+</pre></div></div>
+<p>In general, in SQL++, SQL-style join queries can also be expressed by <tt>UNNEST</tt> clauses and left outer join queries can be expressed by <tt>LEFT OUTER UNNESTs</tt>.</p></div></div>
+<div class="section">
+<h2><a name="GROUP_BY_clauses"></a><a name="Group_By_clauses" id="Group_By_clauses">GROUP BY clauses</a></h2>
+<p>The SQL++ <tt>GROUP BY</tt> clause generalizes standard SQL’s grouping and aggregation semantics, but it also retains backward compatibility with the standard (relational) SQL <tt>GROUP BY</tt> and aggregation features.</p>
+<div class="section">
+<h3><a name="Group_variables" id="Group_variables">Group variables</a></h3>
+<p>In a <tt>GROUP BY</tt> clause, in addition to the binding variable(s) defined for the grouping key(s), SQL++ allows a user to define a <i>group variable</i> by using the clause’s <tt>GROUP AS</tt> extension to denote the resulting group. After grouping, then, the query’s in-scope variables include the grouping key’s binding variables as well as this group variable which will be bound to one collection value for each group. This per-group collection (i.e., multiset) value will be a set of nested objects in which each field of the object is the result of a renamed variable defined in parentheses following the group variable’s name. The <tt>GROUP AS</tt> syntax is as follows:</p>
+
+<div class="source">
+<div class="source">
+<pre><GROUP> <AS> Variable ("(" Variable <AS> VariableReference ("," Variable <AS> VariableReference )* ")")?
+</pre></div></div>
+<div class="section">
+<div class="section">
+<h5><a name="Example"></a>Example</h5>
+
+<div class="source">
+<div class="source">
+<pre>SELECT *
+FROM GleambookMessages message
+GROUP BY message.authorId AS uid GROUP AS msgs(message AS msg);
+</pre></div></div>
+<p>This first example query returns:</p>
+
+<div class="source">
+<div class="source">
+<pre>[ {
+ "msgs": [
+ {
+ "msg": {
+ "senderLocation": [
+ 38.97,
+ 77.49
+ ],
+ "inResponseTo": 1,
+ "messageId": 11,
+ "authorId": 1,
+ "message": " can't stand at&t its plan is terrible"
+ }
+ },
+ {
+ "msg": {
+ "senderLocation": [
+ 41.66,
+ 80.87
+ ],
+ "inResponseTo": 4,
+ "messageId": 2,
+ "authorId": 1,
+ "message": " dislike iphone its touch-screen is horrible"
+ }
+ },
+ {
+ "msg": {
+ "senderLocation": [
+ 37.73,
+ 97.04
+ ],
+ "inResponseTo": 2,
+ "messageId": 4,
+ "authorId": 1,
+ "message": " can't stand at&t the network is horrible:("
+ }
+ },
+ {
+ "msg": {
+ "senderLocation": [
+ 40.33,
+ 80.87
+ ],
+ "inResponseTo": 11,
+ "messageId": 8,
+ "authorId": 1,
+ "message": " like verizon the 3G is awesome:)"
+ }
+ },
+ {
+ "msg": {
+ "senderLocation": [
+ 42.5,
+ 70.01
+ ],
+ "inResponseTo": 12,
+ "messageId": 10,
+ "authorId": 1,
+ "message": " can't stand motorola the touch-screen is terrible"
+ }
+ }
+ ],
+ "uid": 1
+}, {
+ "msgs": [
+ {
+ "msg": {
+ "senderLocation": [
+ 31.5,
+ 75.56
+ ],
+ "inResponseTo": 1,
+ "messageId": 6,
+ "authorId": 2,
+ "message": " like t-mobile its platform is mind-blowing"
+ }
+ },
+ {
+ "msg": {
+ "senderLocation": [
+ 48.09,
+ 81.01
+ ],
+ "inResponseTo": 4,
+ "messageId": 3,
+ "authorId": 2,
+ "message": " like samsung the plan is amazing"
+ }
+ }
+ ],
+ "uid": 2
+} ]
+</pre></div></div>
+<p>As we can see from the above query result, each group in the example query’s output has an associated group variable value called <tt>msgs</tt> that appears in the <tt>SELECT *</tt>’s result. This variable contains a collection of objects associated with the group; each of the group’s <tt>message</tt> values appears in the <tt>msg</tt> field of the objects in the <tt>msgs</tt> collection.</p>
+<p>The group variable in SQL++ makes more complex, composable, nested subqueries over a group possible, which is important given the more complex data model of SQL++ (relative to SQL). As a simple example of this, as we really just want the messages associated with each user, we might wish to avoid the “extra wrapping” of each message as the <tt>msg</tt> field of a object. (That wrapping is useful in more complex cases, but is essentially just in the way here.) We can use a subquery in the <tt>SELECT</tt> clase to tunnel through the extra nesting and produce the desired result.</p></div>
+<div class="section">
+<h5><a name="Example"></a>Example</h5>
+
+<div class="source">
+<div class="source">
+<pre>SELECT uid, (SELECT VALUE g.msg FROM g) AS msgs
+FROM GleambookMessages gbm
+GROUP BY gbm.authorId AS uid
+GROUP AS g(gbm as msg);
+</pre></div></div>
+<p>This variant of the example query returns:</p>
+
+<div class="source">
+<div class="source">
+<pre> [ {
+ "msgs": [
+ {
+ "senderLocation": [
+ 38.97,
+ 77.49
+ ],
+ "inResponseTo": 1,
+ "messageId": 11,
+ "authorId": 1,
+ "message": " can't stand at&t its plan is terrible"
+ },
+ {
+ "senderLocation": [
+ 41.66,
+ 80.87
+ ],
+ "inResponseTo": 4,
+ "messageId": 2,
+ "authorId": 1,
+ "message": " dislike iphone its touch-screen is horrible"
+ },
+ {
+ "senderLocation": [
+ 37.73,
+ 97.04
+ ],
+ "inResponseTo": 2,
+ "messageId": 4,
+ "authorId": 1,
+ "message": " can't stand at&t the network is horrible:("
+ },
+ {
+ "senderLocation": [
+ 40.33,
+ 80.87
+ ],
+ "inResponseTo": 11,
+ "messageId": 8,
+ "authorId": 1,
+ "message": " like verizon the 3
<TRUNCATED>