This is the table structure:
CREATE TABLE IF NOT EXISTS cronlist (
batchnum varchar(18) NOT NULL,
batchflag enum('P','N','R','D','T') NOT NULL DEFAULT 'P',
sendDateTime datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
datesent date NOT NULL,
actualtimestarted datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
timestarted time NOT NULL,
subject varchar(100) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
message mediumtext CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
attach1 varchar(100) NOT NULL,
attach2 varchar(100) NOT NULL,
timelastsent time NOT NULL,
UNIQUE KEY batchnum (batchnum) USING BTREE,
KEY batchflag (batchflag) USING BTREE
) ENGINE=MyISAM DEFAULT CHARSET=latin1 COLLATE=latin1_swedish_ci ROW_FORMAT=DYNAMIC COMMENT='list of email jobs';
If I run the query:
SELECT * FROM cronlist WHERE batchnum = "2026-02-1913:22:50"
and try to edit any field in the resulting row, I can not and sometimes (the worst times of course) HeidiSQL locks up. I can't do anything other than go to the Task Manager and close HeidiSQL.
Same thing if I click on this table and click the Data tab.
The only way that I can edit the data is if I build a SELECT statement with all columns except for the message column or change the Preferences to 2 grid rows.
You are correct that it may not have been this last update that "caused" the problem. I am not always working in a table with a MEDIUMBLOB trying to change or copy a piece of data. But there was definitely a point where I wasn't having this problem anymore.
I like your idea of displaying a few kb in the grid and keeping the whole content in the back. That is basically what the grid looks like to me anyway.
Thank you for your responsiveness. If you need some real data to work with, I am happy to send you 50 rows or so. Have a great weekend!
Joyce