Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Fix a broken link in lang_select.html. |
|---|---|
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: |
53081e39796ef2695a8ebf9620090659 |
| User & Date: | dan 2010-09-09 09:51:53 |
Context
|
2010-09-09
| ||
| 11:32 | Combine two requirements into one in lang_select.html. check-in: 85d1540336 user: dan tags: trunk | |
| 09:51 | Fix a broken link in lang_select.html. check-in: 53081e3979 user: dan tags: trunk | |
|
2010-09-08
| ||
| 19:01 | Clarifications to lang_select.html check-in: 49e2c0eae6 user: dan tags: trunk | |
Changes
Changes to pages/lang.in.
2646 2647 2648 2649 2650 2651 2652 2653 2654 2655 2656 2657 2658 2659 2660 2661 |
<p>If a FROM clause is specified, the data on which a simple SELECT query
operates comes from the one or more tables or subqueries (SELECT statements
in parenthesis) specified following the FROM keyword. ^A sub-select specified
in the join-source following the FROM clause in a simple SELECT statement is
handled as if it was a table containing the data returned by executing the
sub-select statement. ^Each column of the sub-select dataset inherits the
[collation sequence] and [affinity] of the corresponding expression in the
sub-select statement.
<p>^If there is only a single table in the join-source following the FROM
clause, then the input data used by the SELECT statement is the contents of the
named table. ^If there is more than one table specified as part of the
join-source following the FROM keyword, then the contents of each named table
are joined into a single dataset for the simple SELECT statement to operate on.
Exactly how the data is combined depends on the specific [join-op] and
|
| | |
2646 2647 2648 2649 2650 2651 2652 2653 2654 2655 2656 2657 2658 2659 2660 2661 |
<p>If a FROM clause is specified, the data on which a simple SELECT query operates comes from the one or more tables or subqueries (SELECT statements in parenthesis) specified following the FROM keyword. ^A sub-select specified in the join-source following the FROM clause in a simple SELECT statement is handled as if it was a table containing the data returned by executing the sub-select statement. ^Each column of the sub-select dataset inherits the [collation|collation sequence] and [affinity] of the corresponding expression in the sub-select statement. <p>^If there is only a single table in the join-source following the FROM clause, then the input data used by the SELECT statement is the contents of the named table. ^If there is more than one table specified as part of the join-source following the FROM keyword, then the contents of each named table are joined into a single dataset for the simple SELECT statement to operate on. Exactly how the data is combined depends on the specific [join-op] and |