Fix for Bug #6794 Wrong outcome of update operation of ndb table

This commit is contained in:
unknown 2004-11-28 22:28:36 +01:00
parent 5607539c5b
commit f0af808fcc
3 changed files with 36 additions and 1 deletions

View File

@ -0,0 +1,12 @@
DROP TABLE IF EXISTS t1;
CREATE TABLE t1 (
pk1 INT NOT NULL PRIMARY KEY,
b INT NOT NULL,
c INT NOT NULL
) ENGINE=ndbcluster;
INSERT INTO t1 VALUES (0, 0, 0),(1,1,1);
UPDATE t1 set b = c;
select * from t1 order by pk1;
pk1 b c
0 0 0
1 1 1

View File

@ -0,0 +1,22 @@
-- source include/have_ndb.inc
--disable_warnings
DROP TABLE IF EXISTS t1;
--enable_warnings
#
# Basic test of INSERT in NDB
#
#
# Create a normal table with primary key
#
CREATE TABLE t1 (
pk1 INT NOT NULL PRIMARY KEY,
b INT NOT NULL,
c INT NOT NULL
) ENGINE=ndbcluster;
INSERT INTO t1 VALUES (0, 0, 0),(1,1,1);
UPDATE t1 set b = c;
select * from t1 order by pk1;

View File

@ -110,7 +110,8 @@ int mysql_update(THD *thd,
#ifndef NO_EMBEDDED_ACCESS_CHECKS
table->grant.want_privilege=want_privilege;
#endif
if (setup_fields(thd, 0, update_table_list, fields, 1, 0, 0))
if (setup_fields(thd, 0, update_table_list, fields, 1, 0, 0) ||
setup_fields(thd, 0, update_table_list, values, 1, 0, 0))
DBUG_RETURN(-1); /* purecov: inspected */
if (table->timestamp_field)
{