insert event column number not equal value rows number

[deadspacewii]

this position rarely occur but realy exists，for example，when a insert event happend，there are 10 columns but one of row values only have 9 items，so let the error happend when I build sql statement。how can i avoid this when it happend？

version：v1.11.0

[deadspacewii]

this problem cannot be reproduced， so i ask when the OnRow() function return error，go-mysql will re-parser binlog or execute OnRow() with there param again？

[dveeden]

Hi.

Not sure if I understand this correctly.

Do you do something like this?

INSERT INTO t(id, c1, c2, c3) VALUES
(1, 'a', 'b', 'c'),
(2, 'aa', 'bb')

Or is it like this?

INSERT INTO t(id, c1, c2) VALUES (1, 'a', 'b');
INSERT INTO t(id, c1) VALUES (2, 'aa');

Not really sure how you end up with a table with 10 columns and only 9 values without getting a error?

Do you have example code? Are you using go-mysql/replication and/or go-mysql/client? or something else?

[deadspacewii]

like this > INSERT INTO t(id, c1, c2, c3) VALUES

(1, 'a', 'b', 'c'),
(2, 'aa', 'bb')
Or is it like this?

[deadspacewii]

this error happend every year once， so I cannot reproduced this problem

[dveeden]

Could you share logging/output from when it happens? Maybe a code snippet of where it happens?

[deadspacewii]

Could you share logging/output from when it happens? Maybe a code snippet of where it happens?

sorry，it happend two week ago，but if it occur again，I will share logging with you immediately。my purpose is do you or someone see this problem before？I don’t know is it due to go-mysql version