Drizzle

updating primary key in table fails to produce correct output in transaction_log/transaction_reader

Bug #480710 reported by Joe Daly on 2009-11-11

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Drizzle	Fix Released	Critical	Jay Pipes	Drizzle bell "bell"

Bug Description

I created the following test for the transaction_log test suite that produces incorrect output: (note the update statement at the end of the bug report)

Heres the test:

--disable_warnings
DROP TABLE IF EXISTS t1;
--enable_warnings

CREATE TABLE t1 (
id INT NOT NULL
, padding VARCHAR(200) NOT NULL
, PRIMARY KEY (id)
);

INSERT INTO t1 VALUES (1, "I love testing.");
INSERT INTO t1 VALUES (2, "I hate testing.");

UPDATE t1 SET id=4 WHERE id=2;

Here is what is produced by the transaction_reader:

CREATE TABLE t1 ( id INT NOT NULL , padding VARCHAR(200) NOT NULL , PRIMARY KEY (id) );
INSERT INTO `test`.`t1` (`id`,`padding`) VALUES (1,'I love testing.');
INSERT INTO `test`.`t1` (`id`,`padding`) VALUES (2,'I hate testing.');
UPDATE `test`.`t1` SET `id`=4 WHERE `id`=4; <------- should be id=2

The update statement is not correct above.

Related branches

lp:~jaypipes/drizzle/transaction_log

Merged into lp:~drizzle-trunk/drizzle/development

Brian Aker: Pending requested 2009-12-23

Drizzle Developers: Pending requested 2009-12-23

Jay Pipes (jaypipes) on 2009-11-11

Changed in drizzle:
assignee:	nobody → Jay Pipes (jaypipes)
importance:	Undecided → Critical
status:	New → Confirmed
milestone:	none → bell