MySQL Bugs: #55555: "Open value in Viewer" does not work for LONGTEXT columns?

Bug #55555	"Open value in Viewer" does not work for LONGTEXT columns?
Submitted:	26 Jul 2010 11:46	Modified:	29 Aug 2010 4:57
Reporter:	Craig Fowler	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S3 (Non-critical)
Version:	5.2.25	OS:	Linux (Debian Squeeze 32-bit/Ubuntu 9.10 .deb package)
Assigned to:		CPU Architecture:	Any
Tags:	dialog, SELECT, viewer

Description:
The viewer dialog for inspecting the content of a column seems not to support LONGTEXT columns.

Perhaps this is by design - is there a potential performance issue of pulling the contents of a LONGTEXT columns from the db server?

Perhaps it was meant to work and this is a bug?

How to repeat:
1)  Connect to a database that contains a LONGTEXT column within one of its tables (and has some content in that column).

2)  Write and perform a SELECT query that displays the content of that LONGTEXT column.

3)  Right-click on the result and choose "Open value in Viewer"

Nothing happens, where I would expect the viewer dialog to be opened with the contents of that column.

Suggested fix:
If this is !Bg and it is by design that the viewer does not work with LONGTEXT columns then could I request a small dialog box that says as much please?  At the moment it seems like a bug (even if it is not).

That way - if someone tries to view an unsupported column type in the viewer, they at least get a message telling them that it's unsupported.

Works for me on Mac OS X. Looks like Linux-specific bug.

I forgot to say - albeit implied - I can view the contents of other columns in the viewer dialog.  It's just LONGTEXT ones that don't work.

I couldn't repeat on Fedora 13 X86_64.

Hrm.  Odd.

I think I may have nailed this one down a bit better though.  It occurred to me that the mysql servers that I use for production/staging are 5.0.x, specifically:

Server version: 5.0.51a-24+lenny4 (Debian)

I tried reproducing this bug against a more up-to-date MySQL server version running on my laptop (which is Debian testing/squeeze, not Debian stable/lenny):

Server version: 5.1.47-1 (Debian)

And I couldn't reproduce it there.

So, to clarify:

Against a 5.0.51a server I ran the following commands

CREATE TABLE foo (foo_id INT NOT NULL PRIMARY KEY, bar LONGTEXT);
INSERT INTO foo VALUES (1, 'foo bar baz');
SELECT * FROM foo;

In the results pane I right-clicked the output for `bar` and chose to "Open value in Viewer" and nothing happened.  No viewer dialog and no error message.

I then connected to a 5.1.47 server and tried the same script, right-clicked the `bar` column's result and chose to open in the viewer and it worked as expected - I saw the viewer dialog with the correct contents.

If it's an easy thing to fix the functionality within WB against MySQL server version 5.0.51 then I would appreciate it very much.  Equally I appreciate that server 5.0.x is EOL and no longer officially supported so if it's going to be a lot of work then I will understand if this is a WONTFIX.

Hello Craig,

I am not able to reproduce this by using Debian and MySQL 5.0.91.

MySQL 5.0.51a is really old.

Actual MySQL versions are 5.0.91 and 5.1.48

Maybe upgrading your MySQL 5.0 already will solve the problem.

You will find our download archives here now:
http://downloads.mysql.com/archives.php

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".