We are using commcare-export tool to export data to MySQL database. We have
a table in which there are 252 columns, and on exporting this data, we are
getting following error from commcare-export tool.
The error message is:
sqlalchemy.exc.OperationalError: (_mysql_exceptions.OperationalError)
(1118, 'Ro w size too large (> 8126). Changing some columns to TEXT or BLOB may help.
In cu rrent row format, BLOB prefix of 0 bytes is stored inline.') [SQL: u'ALTER
TABLE
I suggest you follow the hints in the error message:
change any long varchar columns to TEXT
···
On 23 January 2017 at 15:12, Ajay Singh wrote:
Hi,
We are using commcare-export tool to export data to MySQL database. We
have a table in which there are 252 columns, and on exporting this data, we
are getting following error from commcare-export tool.
The error message is:
sqlalchemy.exc.OperationalError: (_mysql_exceptions.OperationalError)
(1118, 'Ro w size too large (> 8126). Changing some columns to TEXT or BLOB may
help. In cu rrent row format, BLOB prefix of 0 bytes is stored inline.') [SQL:
u'ALTER TABLE
But it is the case of error in export command only, where we are passing
path of query file.
So in the export command (commcare-export), where can we put TEXT data type
for long varchar fields. During this process commcare-export tool
automatically assigns varchar(32) or TEXT data type from its own
logic/algorithm.
We are using commcare-export tool to export data to MySQL database. We
have a table in which there are 252 columns, and on exporting this data, we
are getting following error from commcare-export tool.
The error message is:
sqlalchemy.exc.OperationalError: (_mysql_exceptions.OperationalError)
(1118, 'Ro w size too large (> 8126). Changing some columns to TEXT or BLOB may
help. In cu rrent row format, BLOB prefix of 0 bytes is stored inline.') [SQL:
u'ALTER TABLE
Increase the value of the "innodb_log_file_size" parameter in your
MySQL config file ("my.ini")
Set "innodb_strict_mode" to "0" in your MySQL config file ("my.ini")
Change to using MyISAM table formats
···
On 23 January 2017 at 15:25, Ajay Singh wrote:
Thanks Simon for prompt reply,
But it is the case of error in export command only, where we are passing
path of query file.
So in the export command (commcare-export), where can we put TEXT data
type for long varchar fields. During this process commcare-export tool
automatically assigns varchar(32) or TEXT data type from its own
logic/algorithm.
We are using commcare-export tool to export data to MySQL database. We
have a table in which there are 252 columns, and on exporting this data, we
are getting following error from commcare-export tool.
The error message is:
sqlalchemy.exc.OperationalError: (_mysql_exceptions.OperationalError)
(1118, 'Ro w size too large (> 8126). Changing some columns to TEXT or BLOB may
help. In cu rrent row format, BLOB prefix of 0 bytes is stored inline.') [SQL:
u'ALTER TABLE
But it is the case of error in export command only, where we are passing
path of query file.
So in the export command (commcare-export), where can we put TEXT data
type for long varchar fields. During this process commcare-export tool
automatically assigns varchar(32) or TEXT data type from its own
logic/algorithm.
We are using commcare-export tool to export data to MySQL database. We
have a table in which there are 252 columns, and on exporting this data, we
are getting following error from commcare-export tool.
The error message is:
sqlalchemy.exc.OperationalError: (_mysql_exceptions.OperationalError)
(1118, 'Ro w size too large (> 8126). Changing some columns to TEXT or BLOB may
help. In cu rrent row format, BLOB prefix of 0 bytes is stored inline.') [SQL:
u'ALTER TABLE