Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Update requirements marks and test cases for multi-VALUE INSERT and to fix typos in requirements text. |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: |
81d9ee0f0df7f283e69ba1c2845339ea |
| User & Date: | drh 2012-12-11 19:40:03 |
Context
|
2012-12-12
| ||
| 13:36 | Version 3.7.15 check-in: cd0b37c5 user: dan tags: trunk, release, version-3.7.15 | |
|
2012-12-11
| ||
| 19:40 | Update requirements marks and test cases for multi-VALUE INSERT and to fix typos in requirements text. check-in: 81d9ee0f user: drh tags: trunk | |
| 19:10 | Fix a typo in a comment that is used to generate documentation. No changes to code. check-in: e38adb60 user: drh tags: trunk | |
Changes
Changes to test/e_insert.test.
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
...
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
|
82 "INSERT OR IGNORE INTO a1 (b, a) VALUES(1, 2),(3,4)" {}
83 "REPLACE INTO a1 (b, a) VALUES(1, 2),(3,4)" {}
84 "REPLACE INTO main.a1 (b, a) VALUES(1, 2),(3,4)" {}
}
delete_all_data
# EVIDENCE-OF: R-20288-20462 The first form (with the "VALUES" keyword)
# creates a single new row in an existing table.
#
do_insert_tests e_insert-1.1 {
0 "SELECT count(*) FROM a2" {0}
1a "INSERT INTO a2 VALUES(1, 2, 3)" {}
1b "SELECT count(*) FROM a2" {1}
2a "INSERT INTO a2(a, b) VALUES(1, 2)" {}
2b "SELECT count(*) FROM a2" {2}
}
# EVIDENCE-OF: R-36040-20870 If no column-list is specified then the
# number of values must be the same as the number of columns in the
# table.
#
# A test in the block above verifies that if the VALUES list has the
# correct number of columns (for table a2, 3 columns) works. So these
# tests just show that other values cause an error.
#
do_insert_tests e_insert-1.2 -error {
table %s has %d columns but %d values were supplied
................................................................................
} {
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}
2a "INSERT INTO a2 VALUES('abc', NULL, 3*3+1)" {}
2b "SELECT * FROM a2 WHERE oid=last_insert_rowid()" {abc {} 10}
3a "INSERT INTO a2 VALUES((SELECT count(*) FROM a2), 'x', 'y')" {}
3b "SELECT * FROM a2 WHERE oid=last_insert_rowid()" {2 x y}
}
# EVIDENCE-OF: R-62524-00361 If a column-list is specified, then the
# number of values must match the number of specified columns.
#
do_insert_tests e_insert-1.4 -error {
%d values for %d columns
} {
1 "INSERT INTO a2(a, b, c) VALUES(1)" {1 3}
2 "INSERT INTO a2(a, b, c) VALUES(1,2)" {2 3}
3 "INSERT INTO a2(a, b, c) VALUES(1,2,3,4)" {4 3}
|
|
|
|
>
>
|
>
|
>
|
<
|
|
|
>
|
>
|
|
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
...
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
|
82 "INSERT OR IGNORE INTO a1 (b, a) VALUES(1, 2),(3,4)" {}
83 "REPLACE INTO a1 (b, a) VALUES(1, 2),(3,4)" {}
84 "REPLACE INTO main.a1 (b, a) VALUES(1, 2),(3,4)" {}
}
delete_all_data
# EVIDENCE-OF: R-21490-41092 The first form (with the "VALUES" keyword)
# creates one or more new rows in an existing table.
#
do_insert_tests e_insert-1.1 {
0 "SELECT count(*) FROM a2" {0}
1a "INSERT INTO a2 VALUES(1, 2, 3)" {}
1b "SELECT count(*) FROM a2" {1}
2a "INSERT INTO a2(a, b) VALUES(1, 2)" {}
2b "SELECT count(*) FROM a2" {2}
3a "INSERT INTO a2(a) VALUES(3),(4)" {}
3b "SELECT count(*) FROM a2" {4}
}
# EVIDENCE-OF: R-53616-44976 If no column-list is specified then the
# number of values inserted into each row must be the same as the number
# of columns in the table.
#
# A test in the block above verifies that if the VALUES list has the
# correct number of columns (for table a2, 3 columns) works. So these
# tests just show that other values cause an error.
#
do_insert_tests e_insert-1.2 -error {
table %s has %d columns but %d values were supplied
................................................................................
} {
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-34231-22576 In this case the result of evaluating the
# left-most expression in each term of the VALUES list is inserted into
# the left-most column of the each new row, and forth for each
# subsequent expression.
#
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}
2a "INSERT INTO a2 VALUES('abc', NULL, 3*3+1)" {}
2b "SELECT * FROM a2 WHERE oid=last_insert_rowid()" {abc {} 10}
3a "INSERT INTO a2 VALUES((SELECT count(*) FROM a2), 'x', 'y')" {}
3b "SELECT * FROM a2 WHERE oid=last_insert_rowid()" {2 x y}
}
# EVIDENCE-OF: R-44710-64652 If a column-list is specified, then the
# number of values in each term of the VALUS list must match the number
# of specified columns.
#
do_insert_tests e_insert-1.4 -error {
%d values for %d columns
} {
1 "INSERT INTO a2(a, b, c) VALUES(1)" {1 3}
2 "INSERT INTO a2(a, b, c) VALUES(1,2)" {2 3}
3 "INSERT INTO a2(a, b, c) VALUES(1,2,3,4)" {4 3}
|
Changes to test/e_uri.test.
257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 |
7 {file:test.db?mode=memory} {not an error}
8 {file:test.db?mode=MEMORY} {no such access mode: MEMORY}
" {
do_test 7.$tn { open_uri_error $uri } $error
}
# EVIDENCE-OF: R-09651-31805 If "ro" is specified, then the database is
# opened for read-only access, just as if the SQLITE_OPEN_READONLY flag
# had been set in the third argument to sqlite3_prepare_v2().
#
# EVIDENCE-OF: R-40137-26050 If the mode option is set to "rw", then the
# database is opened for read-write (but not create) access, as if
# SQLITE_OPEN_READWRITE (but not SQLITE_OPEN_CREATE) had been set.
#
# EVIDENCE-OF: R-26845-32976 Value "rwc" is equivalent to setting both
# SQLITE_OPEN_READWRITE and SQLITE_OPEN_CREATE.
|
| | |
257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 |
7 {file:test.db?mode=memory} {not an error}
8 {file:test.db?mode=MEMORY} {no such access mode: MEMORY}
" {
do_test 7.$tn { open_uri_error $uri } $error
}
# EVIDENCE-OF: R-43036-46756 If "ro" is specified, then the database is
# opened for read-only access, just as if the SQLITE_OPEN_READONLY flag
# had been set in the third argument to sqlite3_open_v2().
#
# EVIDENCE-OF: R-40137-26050 If the mode option is set to "rw", then the
# database is opened for read-write (but not create) access, as if
# SQLITE_OPEN_READWRITE (but not SQLITE_OPEN_CREATE) had been set.
#
# EVIDENCE-OF: R-26845-32976 Value "rwc" is equivalent to setting both
# SQLITE_OPEN_READWRITE and SQLITE_OPEN_CREATE.
|