diff options
author | drh <> | 2021-07-05 00:07:39 +0000 |
---|---|---|
committer | drh <> | 2021-07-05 00:07:39 +0000 |
commit | 105c4b5cedea28a1d06f5331b64b002ebda0e93b (patch) | |
tree | b498cc0b56e797b6c62d0c25a7a55b1a53359ddf /test/misc1.test | |
parent | 4a4e02bc52815acc088702122f8ef4fab27df11c (diff) | |
download | sqlite-105c4b5cedea28a1d06f5331b64b002ebda0e93b.tar.gz sqlite-105c4b5cedea28a1d06f5331b64b002ebda0e93b.zip |
Fix an incorrect comment on testcase misc1-27.0. No changes to code.
FossilOrigin-Name: 49829ae3229b7c7c7adeaa970a84aebd5157bc93b38fd6d80d86cc03f5fdde6f
Diffstat (limited to 'test/misc1.test')
-rw-r--r-- | test/misc1.test | 9 |
1 files changed, 8 insertions, 1 deletions
diff --git a/test/misc1.test b/test/misc1.test index c14a31ebd..758d4082e 100644 --- a/test/misc1.test +++ b/test/misc1.test @@ -728,7 +728,14 @@ do_execsql_test misc1-26.0 { # 2017-12-29 # # The following behaviors (duplicate column names on an INSERT or UPDATE) -# are undocumented. These tests are added to ensure that historical behavior +# are undocumented. <<--- Not so. There is a long-standing requirement +# in lang_update.in to say that when the columns to be updated appear more +# than once in an UPDATE statement that only the rightmost expression is used. +# See e_update-1.6.* for the tests. This is unfortunate, since omitting +# that requirement would greatly simplify the fix to the problem identified +# by forum post https://sqlite.org/forum/info/16ca0e9f32c38567 +# +# These tests are added to ensure that historical behavior # does not change accidentally. # # For duplication columns on an INSERT, the first value is used. |