Customize Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorized as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

No cookies to display.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

No cookies to display.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

No cookies to display.

Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement cookies are used to provide visitors with customized advertisements based on the pages you visited previously and to analyze the effectiveness of the ad campaigns.

No cookies to display.

ndzlogo-1-1
12%
Loading ...

INDIA – HEADQUARTERS

INDIA

UNITED STATES

CANADA

Error:

SQLSTATE[42000]: Syntax error or access violation: 1118 Row size too
large (> 8126). Changing some columns to TEXT or BLOB or using
ROW_FORMAT=DYNAMIC or ROW_FORMAT=COMPRESSED may help. In current row
format, BL OB prefix of 768 bytes is stored inline.

Suggestions to fix the errors:

The error is about a row exceeding mysql max row length limitation. You need to review the create table statement and either;

    *Reduce certain column lengths
    *Change some varchar columns' data type to text or blob
    *Change the row format as suggested in the error message
    *Change character encoding to sg that fits your requirements, but uses less bytes.
    *Change table engine from InnoDB to MyISAM