| Bug #98012 | Replication error 1677, wrong column number | ||
|---|---|---|---|
| Submitted: | 17 Dec 2019 20:53 | Modified: | 10 Jul 2020 12:21 |
| Reporter: | Carlos Tutte | Email Updates: | |
| Status: | Verified | Impact on me: | |
| Category: | MySQL Server: Replication | Severity: | S4 (Feature request) |
| Version: | 5.7 and 8.0 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
[10 Jul 2020 12:21]
MySQL Verification Team
Hi Mr. Tutte, Thank you for your feature request. This is a small, but welcome addition ..... Verified as reported.

Description: Error message displayed is misleading, as it shows index number instead of column order number, i.e count goes 0,1,2,3 and so on instead of 1,2,3,4 Error message is: Last_SQL_Errno: 1677 Last_SQL_Error: Column 0 of table 'test.t1' cannot be converted from type 'tinyblob' to type 'longblob' How to repeat: Master: create database test; use test; CREATE TABLE t1 (name tinyblob, id int auto_increment primary key); Slave: use test; ALTER TABLE t1 MODIFY name longblob; Master: INSERT INTO t1 (id, name) VALUES (1, "name"); Slave: SHOW SLAVE STATUS \G Suggested fix: For error.log printing, use column number starting from 1