Comments - Can we extend the max length of the data types varchar and varbinary to 65535?
Content reproduced on this site is the property of its respective owners,
and this content is not reviewed in advance by MariaDB. The views, information and opinions
expressed by this content do not necessarily represent those of MariaDB or any other party.
I believe the big problem of not having TEXT/BLOBs data types is that the amount of columns supported by the engine columnstore is very limited, around 400 columns if most of them are structured data. Although that is reasonable in OLTP environments, it is not acceptable in OLAP .
I think my use case is very common. We have a 1500 columns table where each row stores all the data of a single transaction (IP addresses, messages sent/received, subscriber data,...). Many of the columns of the table are TINYTEXT. In order to create the table in the columnstore engine, we changed all those columns to varchar(256), but it wasn't possible because we kept getting the error:
"Row size too large. The maximum row size for the used table type, not counting BLOBs, is 65535"
The only way to create the table was to reduce the amount of columns to less than 350. We can't loose that many columns in production environments.
That's the reason why I believe MCOL-267 and MCOL-356 should have a higher priority.
Thanks for the feedback. The row size (and max number of columns of 4096) is a limit enforced by the mariadb server derived from the original mysql code base.
I understand, but let's agree than the TEXT and BLOB columns are no limited by the row limit size of 65536 bytes and to have a limit of 300 max columns is very different than 4096
Also the best way for you and the community to help us in prioritizing improvements and bugs is to use the jira 'vote for this issue' function on the improvements to indicate this would be something that would be beneficial to your use case.