Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Fix a hyperlink in the SELECT documentation. |
|---|---|
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: |
1c86b01b954f15484296d1d6b0f05f20 |
| User & Date: | drh 2014-02-05 00:16:30 |
Context
|
2014-02-06
| ||
| 13:25 | Fix an example code error in the WITH documentation. check-in: a6ce882b01 user: drh tags: trunk | |
|
2014-02-05
| ||
| 00:16 | Fix a hyperlink in the SELECT documentation. check-in: 1c86b01b95 user: drh tags: trunk | |
|
2014-02-03
| ||
| 14:00 | Add the sha1sum and SQLITE_SOURCE_ID for version 3.8.3 to the changelog. check-in: c161234538 user: dan tags: trunk | |
Changes
Changes to pages/lang.in.
3778 3779 3780 3781 3782 3783 3784 3785 3786 3787 3788 3789 3790 3791 3792 3793 |
<tcl>hd_fragment crossjoin {treats the CROSS JOIN operator specially}</tcl>
<p><b>Side note: Special handling of CROSS JOIN.</b>
^There is no difference between the "INNER JOIN", "JOIN" and "," join
operators. They are completely interchangeable in SQLite.
^(The "CROSS JOIN" join operator produces the same result as the
"INNER JOIN", "JOIN" and "," operators)^, but is
<a href=optoverview.html#crossjoin>handled differently by the query
optimizer</a> in that it prevents the query optimizer from reordering
the tables in the join. An application programmer can use the CROSS JOIN
operator to directly influence the algorithm that is chosen to implement
the SELECT statement. Avoid using CROSS JOIN except in specific situations
where manual control of the query optimizer is desired. Avoid using
CROSS JOIN early in the development of an application as doing so is
a <a href="http://c2.com/cgi/wiki?PrematureOptimization">premature
optimization</a>. The special handling of CROSS JOIN is an SQLite-specific
|
| | |
3778 3779 3780 3781 3782 3783 3784 3785 3786 3787 3788 3789 3790 3791 3792 3793 |
<tcl>hd_fragment crossjoin {treats the CROSS JOIN operator specially}</tcl>
<p><b>Side note: Special handling of CROSS JOIN.</b>
^There is no difference between the "INNER JOIN", "JOIN" and "," join
operators. They are completely interchangeable in SQLite.
^(The "CROSS JOIN" join operator produces the same result as the
"INNER JOIN", "JOIN" and "," operators)^, but is
[CROSS JOIN|handled differently by the query optimizer]
in that it prevents the query optimizer from reordering
the tables in the join. An application programmer can use the CROSS JOIN
operator to directly influence the algorithm that is chosen to implement
the SELECT statement. Avoid using CROSS JOIN except in specific situations
where manual control of the query optimizer is desired. Avoid using
CROSS JOIN early in the development of an application as doing so is
a <a href="http://c2.com/cgi/wiki?PrematureOptimization">premature
optimization</a>. The special handling of CROSS JOIN is an SQLite-specific
|