[MDEV-20268] create table fails with row size too large in 10.3 but not 10.1 Created: 2019-08-06  Updated: 2020-08-25  Resolved: 2019-08-06

Status: Closed
Project: MariaDB Server
Component/s: Server
Affects Version/s: 10.3.17
Fix Version/s: N/A

Type: Bug Priority: Critical
Reporter: Rick Pizzi Assignee: Eugene Kosov (Inactive)
Resolution: Duplicate Votes: 1
Labels: None

Issue Links:
Duplicate
is duplicated by MDEV-20256 "Row size too large" on latest releas... Closed
Relates
relates to MDEV-16969 Fix error message as promised in upst... Open
relates to MDEV-19292 "Row size too large" error when creat... Closed
relates to MDEV-20448 Add link to release notes about "Row ... Closed
relates to MDEV-23521 Implement an InnoDB row format that c... Open

 Description   

The following create table fails on 10.3 but works fine on 10.1.

Error is: Row size too large (> 8126). Changing some columns to TEXT or BLOB may help. In current row format, BLOB prefix of 0 bytes is stored inline.

How to reproduce:

CREATE TABLE `orders` (   `id` int(11) NOT NULL AUTO_INCREMENT,   `field1` varchar(255) DEFAULT NULL,   `field2` varchar(255) DEFAULT NULL,   `creationDate` datetime DEFAULT NULL,   `modificationDate` datetime DEFAULT NULL,   `modifiedBy` varchar(255) DEFAULT NULL,   `modifiedBySystem` varchar(255) DEFAULT NULL,   `field4` datetime DEFAULT NULL,   `field5` varchar(255) DEFAULT NULL,   `field6` varchar(255) DEFAULT NULL,   `field7` varchar(255) DEFAULT NULL,   `field8` datetime DEFAULT NULL,   `fuffa` varchar(255) DEFAULT NULL,   `field9` varchar(255) DEFAULT NULL,   `field10` varchar(255) DEFAULT NULL,   `fuffa2` datetime DEFAULT NULL,   `field11` varchar(255) DEFAULT NULL,   `field12` varchar(255) DEFAULT NULL,   `field13` varchar(255) DEFAULT NULL,   `field14` varchar(255) DEFAULT NULL,   `field15` varchar(255) DEFAULT NULL,   `field16` varchar(255) DEFAULT NULL,   `field17` int(11) DEFAULT NULL,   `field18` varchar(255) DEFAULT NULL,   `field19` varchar(255) DEFAULT NULL,   `field20` varchar(255) DEFAULT NULL,   `field21` varchar(255) DEFAULT NULL,   `field22` int(11) DEFAULT NULL,   `field23` varchar(255) DEFAULT NULL,   `field24` varchar(255) DEFAULT NULL,   `field25` varchar(255) DEFAULT NULL,   `field26` varchar(255) DEFAULT NULL,   `field27` varchar(255) DEFAULT NULL,   `field28` varchar(255) DEFAULT NULL,   `field29` varchar(255) DEFAULT NULL,   `field30` varchar(255) DEFAULT NULL,   `field31` int(11) DEFAULT NULL,   `field32` varchar(255) DEFAULT NULL,   `field33` varchar(255) DEFAULT NULL,   `field34` varchar(255) DEFAULT NULL,   `field35` varchar(255) DEFAULT NULL,   `field36` varchar(255) DEFAULT NULL,   `field37` varchar(255) DEFAULT NULL,   `field38` varchar(255) DEFAULT NULL,   `field39` varchar(255) DEFAULT NULL,   `field40` varchar(255) DEFAULT NULL,   `field41` varchar(25T NULL,   `field46` varchar(255) DEFAULT NULL,   `field47` varchar(255) DEFAULT NULL,   `field48` varchar(255) DEFAULT NULL,   `field49` varchar(255) DEFAULT NULL,   `field50` varchar(255) DEFAULT NULL,   `field51` varchar(255) DEFAULT NULL,   `field52` int(11) DEFAULT NULL,   `field53` varchar(255) DEFAULT NULL,   `field54` varchar(255) DEFAULT NULL,   `field55` tinyint(1) DEFAULT NULL,   `field56` varchar(255) DEFAULT NULL,   `field57` varchar(255) DEFAULT NULL,   `field58` varchar(255) DEFAULT NULL,   PRIMARY KEY (`id`)) Engine=InnoDB;
ERROR 1118 (42000): Row size too large (> 8126). Changing some columns to TEXT or BLOB may help. In current row format, BLOB prefix of 0 bytes is stored inline.


Generated at Thu Feb 08 08:58:10 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.