Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Fix some mistakes in lang_select.html. |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: |
55e829f4688b6befd4ded2c2f0300f3f |
| User & Date: | dan 2010-09-06 19:12:50 |
Context
|
2010-09-07
| ||
| 14:58 | Added link to the Belorussion translation of the FAQ. Added links from parameter binding to SQLITE_LIMIT_VARIABLE_NUMBER. Added section to the "How SQLite Is Tested" document describing disabled optimization tests. (check-in: 71ae536af0 user: drh tags: trunk) | |
|
2010-09-06
| ||
| 19:12 | Fix some mistakes in lang_select.html. (check-in: 55e829f468 user: dan tags: trunk) | |
|
2010-09-04
| ||
| 18:36 | Fix a couple of errors in the recent changes to lang_select.html. (check-in: b47f9e77a6 user: dan tags: trunk) | |
Changes
Changes to pages/lang.in.
2667 2668 2669 2670 2671 2672 2673 2674 2675 2676 2677 2678 2679 2680 2681 2682 2683 2684 2685 2686 2687 2688 2689 2690 2691 2692 2693 2694 |
of collation sequence and affinity precedence.
<p>^For each pair of columns identified by a USING clause, the column
from the right-hand dataset is omitted from the joined dataset. ^This
is the only difference between a USING clause and its equivalent ON
constraint.
<li> <p>^If the join-op is a "LEFT JOIN" or "LEFT OUTER JOIN", then the
composite dataset is created as for an "INNER JOIN". ^Except, after
the ON and USING filtering clauses have been applied, an extra row is
added to the output for each row in the original left-hand input
dataset (if any) that corresponds to no rows at all in the composite
dataset. ^The added rows contain NULL values in the columns that would
normally contain values copied from the right-hand input dataset.
<li> <p>^If the NATURAL keyword is added to any of the join-ops, then an
implicit USING clause is added to the join-constraints. The implicit
USING clause contains each of the column names that appear in both
the left and right-hand input datasets. If the left and right-hand
input datasets feature no common column names, then the NATURAL keyword
has no effect on the results of the join.
</ul>
<p>^(When more than two tables are joined together as part of a FROM clause,
the join operations are processed in order from left to right. In other
words, the FROM clause (A join-op-1 B join-op-2 C) is processed as
((A join-op-1 B) join-op-2 C).)^
|
| | | | | | | > |
2667 2668 2669 2670 2671 2672 2673 2674 2675 2676 2677 2678 2679 2680 2681 2682 2683 2684 2685 2686 2687 2688 2689 2690 2691 2692 2693 2694 2695 |
of collation sequence and affinity precedence.
<p>^For each pair of columns identified by a USING clause, the column
from the right-hand dataset is omitted from the joined dataset. ^This
is the only difference between a USING clause and its equivalent ON
constraint.
<li> <p>^(If the join-op is a "LEFT JOIN" or "LEFT OUTER JOIN", then the
composite dataset is created as for an "INNER JOIN". Except, after
the ON or USING filtering clauses have been applied, an extra row is
added to the output for each row in the original left-hand input
dataset (if any) that corresponds to no rows at all in the composite
dataset.)^ ^The added rows contain NULL values in the columns that would
normally contain values copied from the right-hand input dataset.
<li> <p>^(If the NATURAL keyword is added to any of the join-ops, then an
implicit USING clause is added to the join-constraints. The implicit
USING clause contains each of the column names that appear in both
the left and right-hand input datasets.)^ ^If the left and right-hand
input datasets feature no common column names, then the NATURAL keyword
has no effect on the results of the join. ^A USING or ON clause may
not be added to a join that specifies the NATURAL keyword.
</ul>
<p>^(When more than two tables are joined together as part of a FROM clause,
the join operations are processed in order from left to right. In other
words, the FROM clause (A join-op-1 B join-op-2 C) is processed as
((A join-op-1 B) join-op-2 C).)^
|