Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Fix typos in evidence marks on tests. |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: |
bd980be471b185e2dc45875804103d5a |
| User & Date: | drh 2011-06-20 22:34:50 |
Context
|
2011-06-20
| ||
| 23:51 | More typo fixes in evidence marks. No code changes. (check-in: e60eefc7 user: drh tags: trunk) | |
| 22:34 | Fix typos in evidence marks on tests. (check-in: bd980be4 user: drh tags: trunk) | |
| 21:47 | Fix more documentation typos. (check-in: b9cbab73 user: drh tags: trunk) | |
Changes
Changes to test/e_delete.test.
436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 |
2 "DELETE FROM t1 LIMIT 3" {4 5}
3 "DELETE FROM t1 LIMIT 1 OFFSET 0" {2 3 4 5}
4 "DELETE FROM t1 LIMIT 1 OFFSET 1" {1 3 4 5}
5 "DELETE FROM t1 LIMIT 1 OFFSET 2" {1 2 4 5}
}
# EVIDENCE-OF: R-26627-30313 The ORDER BY clause on an DELETE statement
# is used only to determine which rows fall within the LIMIT. The order
# in which rows are deleted is arbitrary and is not influenced by the
# ORDER BY clause.
#
# In practice, rows are always deleted in rowid order.
#
do_delete_tests e_delete-3.10 -repair {
|
| |
436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 |
2 "DELETE FROM t1 LIMIT 3" {4 5}
3 "DELETE FROM t1 LIMIT 1 OFFSET 0" {2 3 4 5}
4 "DELETE FROM t1 LIMIT 1 OFFSET 1" {1 3 4 5}
5 "DELETE FROM t1 LIMIT 1 OFFSET 2" {1 2 4 5}
}
# EVIDENCE-OF: R-07548-13422 The ORDER BY clause on a DELETE statement
# is used only to determine which rows fall within the LIMIT. The order
# in which rows are deleted is arbitrary and is not influenced by the
# ORDER BY clause.
#
# In practice, rows are always deleted in rowid order.
#
do_delete_tests e_delete-3.10 -repair {
|
Changes to test/e_insert.test.
148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 |
} {
1 "INSERT INTO a2 VALUES(1)" {a2 3 1}
2 "INSERT INTO a2 VALUES(1,2)" {a2 3 2}
3 "INSERT INTO a2 VALUES(1,2,3,4)" {a2 3 4}
4 "INSERT INTO a2 VALUES(1,2,3,4,5)" {a2 3 5}
}
# EVIDENCE-OF: R-52422-65517 In this case the result of evaluting the
# left-most expression in the VALUES list is inserted into the left-most
# column of the new row, and so on.
#
delete_all_data
do_insert_tests e_insert-1.3 {
1a "INSERT INTO a2 VALUES(1, 2, 3)" {}
1b "SELECT * FROM a2 WHERE oid=last_insert_rowid()" {1 2 3}
|
| |
148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 |
} {
1 "INSERT INTO a2 VALUES(1)" {a2 3 1}
2 "INSERT INTO a2 VALUES(1,2)" {a2 3 2}
3 "INSERT INTO a2 VALUES(1,2,3,4)" {a2 3 4}
4 "INSERT INTO a2 VALUES(1,2,3,4,5)" {a2 3 5}
}
# EVIDENCE-OF: R-04006-57648 In this case the result of evaluating the
# left-most expression in the VALUES list is inserted into the left-most
# column of the new row, and so on.
#
delete_all_data
do_insert_tests e_insert-1.3 {
1a "INSERT INTO a2 VALUES(1, 2, 3)" {}
1b "SELECT * FROM a2 WHERE oid=last_insert_rowid()" {1 2 3}
|
Changes to test/e_select.test.
1764 1765 1766 1767 1768 1769 1770 1771 1772 1773 1774 1775 1776 1777 1778 1779 1780 |
3 1 8 1 7 1 -20 1 93 1 -1 1 -1 2 93 2
}
4 "SELECT z AS x, x AS z FROM d1 ORDER BY x" {
-20 1 -1 2 -1 1 3 1 7 1 8 1 93 2 93 1
}
}
# EVIDENCE-OF: R-27923-38747 Otherwise, if the ORDER BY expression is
# any other expression, it is evaluated and the the returned value used
# to order the output rows.
#
# EVIDENCE-OF: R-03421-57988 If the SELECT statement is a simple SELECT,
# then an ORDER BY may contain any arbitrary expressions.
#
do_select_tests e_select-8.6 {
1 "SELECT * FROM d1 ORDER BY x+y+z" {
1 2 -20 1 5 -1 1 2 3 2 5 -1
|
| | | |
1764 1765 1766 1767 1768 1769 1770 1771 1772 1773 1774 1775 1776 1777 1778 1779 1780 |
3 1 8 1 7 1 -20 1 93 1 -1 1 -1 2 93 2
}
4 "SELECT z AS x, x AS z FROM d1 ORDER BY x" {
-20 1 -1 2 -1 1 3 1 7 1 8 1 93 2 93 1
}
}
# EVIDENCE-OF: R-65068-27207 Otherwise, if the ORDER BY expression is
# any other expression, it is evaluated and the returned value used to
# order the output rows.
#
# EVIDENCE-OF: R-03421-57988 If the SELECT statement is a simple SELECT,
# then an ORDER BY may contain any arbitrary expressions.
#
do_select_tests e_select-8.6 {
1 "SELECT * FROM d1 ORDER BY x+y+z" {
1 2 -20 1 5 -1 1 2 3 2 5 -1
|
Changes to test/e_uri.test.
44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 |
set e } # EVIDENCE-OF: R-35840-33204 If URI filename interpretation is enabled, # and the filename argument begins with "file:", then the filename is # interpreted as a URI. # # EVIDENCE-OF: R-32637-34037 URI filename interpretation is enabled if # the SQLITE_OPEN_URI flag is is set in the fourth argument to # sqlite3_open_v2(), or if it has been enabled globally using the # SQLITE_CONFIG_URI option with the sqlite3_config() method or by the # SQLITE_USE_URI compile-time option. # if {$tcl_platform(platform) == "unix"} { set flags [list SQLITE_OPEN_READWRITE SQLITE_OPEN_CREATE] |
| | |
44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 |
set e
}
# EVIDENCE-OF: R-35840-33204 If URI filename interpretation is enabled,
# and the filename argument begins with "file:", then the filename is
# interpreted as a URI.
#
# EVIDENCE-OF: R-24124-56960 URI filename interpretation is enabled if
# the SQLITE_OPEN_URI flag is set in the fourth argument to
# sqlite3_open_v2(), or if it has been enabled globally using the
# SQLITE_CONFIG_URI option with the sqlite3_config() method or by the
# SQLITE_USE_URI compile-time option.
#
if {$tcl_platform(platform) == "unix"} {
set flags [list SQLITE_OPEN_READWRITE SQLITE_OPEN_CREATE]
|