2

Using the example in provided by DBForge for COLUMN_LIST against the table assets, when I run the following:

SELECT item_name, column_list(dynamic_cols) FROM assets;

Through DBForge Studio, the resultset for column_list(dynamic_cols) is shown as an image / icon when viewed in Grid mode while it displays `long" in Text mode.

However running the same query with HeidiSQL, I can see the actual comma separated result set for column_list(dynamic_cols).

Is there a result why DBForge Studio doesn't display the comma separated result set? is there a setting I have to change or click in order to view it?

Vincent Savard
  • 34,979
  • 10
  • 68
  • 73
YCY
  • 21
  • 1

1 Answers1

0

The actual version of dbForge Studio for MySQL does not produce such errors. The only exception is the case of having more than 2000 characters in a “cell”. In that case, the data is presented as a symbol – from the 2001st character and further.

enter image description here

It relates to all data types and is caused by optimization. Concerning your data type, Dynamic Columns are used when the number of possible attributes is too high. For instance:

Max number of columns 65535

Max total length of packed dynamic column max_allowed_packet (1G)

Therefore, such optimization is necessary for the Studio to work appropriately.

Devart
  • 119,203
  • 23
  • 166
  • 186