diff options
| author | unknown <guilhem@mysql.com> | 2005-11-07 16:18:46 +0100 |
|---|---|---|
| committer | unknown <guilhem@mysql.com> | 2005-11-07 16:18:46 +0100 |
| commit | 50f48187f2f135b458aee47c561b3afe7df5aa07 (patch) | |
| tree | 7b70cea20c3b819b996a804ba53efafcba9e279a /mysql-test | |
| parent | 21447f17e63d84830f6346aca4877db30215c67d (diff) | |
| download | mariadb-git-50f48187f2f135b458aee47c561b3afe7df5aa07.tar.gz | |
Fix for BUG#14703 "Valgrind error when inserting 0 into a BIT column (like in type_bit.test)":
test "length" first (otherwise when "length" is 0, the *from invalid access still triggers a Valgrind warning).
I wrote to the Valgrind authors in case this is something fixable in Valgrind (normally the
decision to issue a warning is based on the simulated CPU condition code, which should not be undefined here).
BUILD/compile-pentium64-valgrind-max:
putting this script in sync with compile-pentium-valgrind-max, otherwise we didn't have the federated engine compiled in.
mysql-test/r/read_only.result:
result update
sql/field.cc:
To avoid a Valgrind warning running the type_bit test: test "length" first (otherwise when "length" is 0, the *from invalid access still triggers a Valgrind warning).
Diffstat (limited to 'mysql-test')
| -rw-r--r-- | mysql-test/r/read_only.result | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/mysql-test/r/read_only.result b/mysql-test/r/read_only.result index 09a0861e0c4..55a14bcaec8 100644 --- a/mysql-test/r/read_only.result +++ b/mysql-test/r/read_only.result @@ -14,6 +14,8 @@ create table t3 (a int); ERROR HY000: The MySQL server is running with the --read-only option so it cannot execute this statement insert into t1 values(1); ERROR HY000: The MySQL server is running with the --read-only option so it cannot execute this statement +update t1 set a=1 where 1=0; +ERROR HY000: The MySQL server is running with the --read-only option so it cannot execute this statement update t1,t2 set t1.a=t2.a+1 where t1.a=t2.a; ERROR HY000: The MySQL server is running with the --read-only option so it cannot execute this statement delete t1,t2 from t1,t2 where t1.a=t2.a; |