Table Data Truncation

[dhayes]

I ran into an apparent data size limitation using SQLyog (enterprise V5.27, but also occurs on community version 6.07).

The issue is with relatively long varchar fields (1000-4000 characters). When viewing the data on the Table Data tab, if you edit a long varchar field's value directly in the grid (either on purpose or accidentally), the value is truncated to a maximum of 511 characters. Has anyone else hit this limitation?

The project I currently work on has numerous fields of this nature and it's currently not an option to change the field type to text.

[peterlaursen]

confirmed!

test case:

CREATE TABLE `test` (

`n` int(11) NOT NULL,

`t` varchar(5000) default NULL,

PRIMARY KEY (`n`)

)

INSERT INTO test (t) VALUES — t is a varchar(5000)

('aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

aaaaaaaaaaaaaaaaaabbbbbbbbbbcccccccccc'); — 500 a's 10 b's 10 c's

select t from test;

— in DATA TAB and RESULT TAB GRID mode only ONE 'c' is displayed

— in RESULT TAB TEXT mode ALL 'c's are displayed

Basically this is a MySQL 5.0 compability issues that we did not fix. Before version 5.0 MySQL varchars could be only 255 characters.

We should provide an option for user to define the length of string (no matter the type) that should open in the BLOB viewer. For most users I think even a string 100 characters long is too long for the GRID.

Actually it has been here:

http://webyog.com/faq/content/33/20/en/pla…-of-sqlyog.html

.. for long. Always was given 2nd priority!

In the short term we should consider to raise the max witdh of the cell to around 65.600 (if it can be done with the GRID code) to support mySQL 5.0 LONG varchars

[peterlaursen]

I am sorry, but we are not able to fix this in the 6.1 tree. There is too much code depending on the constant '512'.

We will fix in 6.2

[Author]

Posts