Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Minor changes to lang.in. |
|---|---|
| Downloads: | Tarball | ZIP archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: |
8efac9af2bbff420472bd34c490b0ea6 |
| User & Date: | dan 2010-09-10 19:11:05.000 |
Context
|
2010-09-11
| ||
| 17:46 | Change to requirement marks in lang.in. (check-in: b5882b3f8f user: dan tags: trunk) | |
|
2010-09-10
| ||
| 19:11 | Minor changes to lang.in. (check-in: 8efac9af2b user: dan tags: trunk) | |
|
2010-09-09
| ||
| 19:08 | Bug in "fossil rename" prevented the removal of fileformat.in from working. This checkin deletes it, which we know works. (check-in: 95550b75ee user: drh tags: trunk) | |
Changes
Changes to pages/lang.in.
| ︙ | ︙ | |||
2779 2780 2781 2782 2783 2784 2785 |
non-aggregate expression. ^Or, if the dataset contains zero rows, then
each non-aggregate expression is evaluated against a row consisting
entirely of NULL values.
<p>^The single row of result-set data created by evaluating the aggregate
and non-aggregate expressions in the result-set forms the result of an
aggregate query without a GROUP BY clause. ^An aggregate query without a
| | > | | | > | | | | | > | | | < | 2779 2780 2781 2782 2783 2784 2785 2786 2787 2788 2789 2790 2791 2792 2793 2794 2795 2796 2797 2798 2799 2800 2801 2802 2803 2804 2805 2806 2807 2808 2809 2810 2811 2812 2813 |
non-aggregate expression. ^Or, if the dataset contains zero rows, then
each non-aggregate expression is evaluated against a row consisting
entirely of NULL values.
<p>^The single row of result-set data created by evaluating the aggregate
and non-aggregate expressions in the result-set forms the result of an
aggregate query without a GROUP BY clause. ^An aggregate query without a
GROUP BY clause always returns exactly one row of data, even if there are
zero rows of input data.
<li><p>^(If the SELECT statement is <b>an aggregate query with a GROUP
BY</b> clause, then each of the expressions specified as part of the
GROUP BY clause is evaluated for each row of the dataset. Each row
is then assigned to a "group" based on the results; rows for which
the results of evaluating the GROUP BY expressions are the same are
assigned to the same group.)^ ^For the purposes of grouping rows, NULL
values are considered equal. ^The usual rules for [collation|selecting a
collation sequence] with which to compare text values apply when evaluating
expressions in a GROUP BY clause. ^The expressions in the GROUP BY clause
do <em>not</em> have to be expressions that appear in the result. ^The
expressions in a GROUP BY clause may not be aggregate expressions.
<p>^(If a HAVING clause is specified, it is evaluated once for each group
of rows and cast to an integer value. If the result of evaluating the
HAVING clause is NULL or zero (integer value 0), the group is discarded.)^
^If the HAVING clause is an aggregate expression, it is evaluated across
all rows in the group. ^If a HAVING clause is a non-aggregate expression,
it is evaluated with respect to an arbitrarily selected row from the group.
^The HAVING expression may refer to values, even aggregate functions, that
are not in the result.</p>
<p>^Each expression in the result-set is then evaluated once for each
group of rows. ^If the expression is an aggregate expression, it is
evaluated across all rows in the group. ^Otherwise, it is evaluated against
a single arbitrarily chosen row from within the group. ^If there is more
|
| ︙ | ︙ |