Does setting different values for ROW_FORMAT affect TiDB?

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: ROW_FORMAT设置不同的值对TiDB有影响么?

| username: Kongdom

[TiDB Usage Environment] Production Environment
[TiDB Version] v6.5.3
When creating a table and setting ROW_FORMAT=Compact, an error “Row size too large” occurs. Setting ROW_FORMAT=Dynamic works fine.
Since we need to be compatible with both MySQL and TiDB, the table structure needs to be consistent. I would like to ask, does setting ROW_FORMAT to Compact or Dynamic have any impact on TiDB?

| username: zhanggame1 | Original post link

The ROW_FORMAT parameter is ignored in TiDB, so you can set it to anything you like.

CREATE TABLE | PingCAP Documentation Center

| username: tidb菜鸟一只 | Original post link

This is the row format of MySQL. TiDB’s underlying storage is different from MySQL, so you can set this parameter to anything…

| username: Kongdom | Original post link

:call_me_hand: :call_me_hand: :call_me_hand:

| username: Kongdom | Original post link

:+1: :+1: :+1:

| username: Kongdom | Original post link

:wink: You replied quickly, so I’ll give you the best answer.

| username: 大飞哥online | Original post link

In MySQL, there will be a difference. TiDB does not recognize it. When migrating from MySQL, it will be ignored.

| username: Kongdom | Original post link

:sunglasses: This is awesome.

| username: 大飞哥online | Original post link

Thank you, still learning.

| username: Kongdom | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.