mysqli row size too large

[fbf0x3hcos0yxjy]

i am trying to insert data into a mysql table that is using the innodb storage engine and am getting this error:\[code\]Mysqli statement execute error : Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. You have to change some columns to TEXT or BLOBs\[/code\]i understand the error, but my table is made up of almost only text and mediumtext columns.basically, i am trying to store a bunch of xml responses from a web service that are of variable length. i am able to save these responses (the requests happen sequentially in a batch process) until i get to col14, where the insert of the response gives the above errormy backup idea if i can't get this to work is to just save the xml on the server and put the file location in the database.i have included the create table code\[code\]CREATE TABLE IF NOT EXISTS `qb_results` ( `id` int(11) NOT NULL AUTO_INCREMENT, `col1` varchar(32) COLLATE utf8_unicode_ci DEFAULT NULL, `col2` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `col3` text COLLATE utf8_unicode_ci, `col4` text COLLATE utf8_unicode_ci, `col5` text COLLATE utf8_unicode_ci, `col6` text COLLATE utf8_unicode_ci, `col7` mediumtext COLLATE utf8_unicode_ci, `col8` mediumtext COLLATE utf8_unicode_ci, `col9` mediumtext COLLATE utf8_unicode_ci, `col10` mediumtext COLLATE utf8_unicode_ci, `col11` mediumtext COLLATE utf8_unicode_ci, `col12` mediumtext COLLATE utf8_unicode_ci, `col13` mediumtext COLLATE utf8_unicode_ci, `col14` mediumtext COLLATE utf8_unicode_ci, `col15` mediumtext COLLATE utf8_unicode_ci, `col16` mediumtext COLLATE utf8_unicode_ci, `col17` mediumtext COLLATE utf8_unicode_ci, `col18` mediumtext COLLATE utf8_unicode_ci, `updated_time` datetime DEFAULT NULL, PRIMARY KEY (`id`)) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci AUTO_INCREMENT=61 ;\[/code\]edit - changed columns to be numbered because they were business specific and didn't feel it was necessary or relevant to include their actual column names. normalizing would actually solve the problem but still does not explain the error given the context (error says to use text columns, which are being used already)