MySQL Bugs: #8006: field viewer does not allow editting a blob

Bug #8006	field viewer does not allow editting a blob
Submitted:	19 Jan 2005 11:24	Modified:	28 Sep 2005 15:04
Reporter:	bastiaan schupp	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Query Browser	Severity:	S3 (Non-critical)
Version:	1.1.5	OS:	Windows (Windows XP Home SP2)
Assigned to:	Vladimir Kolesnikov	CPU Architecture:	Any

Description:
Hi,

When I want to edit a blob the field pop-up viewer opens in binary mode but does not allow to edit the field. 

- clicking the icon for editting (pen, notice difference to icon in manual, wrench), or using pop-up menu/ 'Edit field in pop-up editor' results in the same thing, only the ability to view the field in binary mode, but not to edit it.

- I did enable editting
- Other field types can be editted using the pop-up viewer
- Clicking the blob in an empty area or on 'blob' results in a cursor that allows entering new information into the blob, overwriting the old information, so this form of 'editting' works
- The blobs I was trying to edit contained text only (i.e. no images)

Oh, I did read the manual: 'Edit: This field looks like a wrench and opens the field viewer in edit mode, allowing you to make changes to the data and apply the changes to the result set.'

This is what I did, except that in 1.1.5 the wrench is apparently replaced by a pen ;-)  

Cheers!

How to repeat:
see above

Could you paste the SQL Create table statement of the table you are trying to edit (right mousebutton on the table in the Schema Tree) and state which column you want to edit?

It is possible to edit TEXT columns but it is not possible to edit BLOB columns at the moment as they could contain zeros in the middle of the string (which would terminate the string since we use C strings). So you could only edit them in the Hex Viewer which is not implemented yet.

If you are editing a VARCHAR or TEXT column and this doesn't work it is indeed a bug.

Thanks!

So, I was indeed trying to edit blobs which is not yet implemented according to you. This turns my bug report into an urgent feature request.

In answer to your question:

CREATE TABLE `Members` (
  `MembID` int(10) unsigned NOT NULL auto_increment,
  `m_Name` varchar(50) default NULL,
  `m_Pict` varchar(100) default NULL,
  `m_RI` blob,
  `m_AROs` blob,
  `m_Bla` blob,
  `m_AROl` blob,
  `m_Appr` blob,
  `m_AcTF` blob,
  `m_FPla` blob,
  `m_LastMod` timestamp(14) NOT NULL,
  `m_cInf` blob,
  PRIMARY KEY  (`MembID`)
) TYPE=MyISAM;

Regards,

B. Schupp

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".

Sorry, this bug was wrongly closed as 'no feedback' despite the fact that user provided feedback . Reopened.

Thanks for your bug report.

This is clearly a bug as the documentation and the Working with Blobs tutorial  says that that one can edit the contents of the fields.

Thanks for verifying. I hope you'll soon be able to solve it.

I've got the same problem with LONGTEXT fields that the original poster had with BLOB's.  

I am using version 1.1.4, the build that comes with the Ubuntu Hoary Linux distribution.

Thank you for your bug report. This issue has already been fixed
in the latest released version of that product, which you can download at 
http://www.mysql.com/downloads/

Additional info:

LONGTEXT is editable, BLOBs are not

As of version 1.1.17, the documentation still says that BLOBs are editable though.  Ref. section 5.6 of the help.

Is there any fix/patch/update that allows edit BLOB using MySQL Query Browser yet ???

Thanks.

Bug fixed with MySQM Query Browser version 1.2.12 in the MySQL GUI 5.0 package.