Interactive clients should hex blob output

Bug #716952 reported by Andrew Hutchings on 2011-02-11
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Drizzle
Wishlist
Unassigned

Bug Description

The drizzle client should indicate that it is in interactive mode and receive blob data in human-readable hex format (or receive the blob and convert it to human-readable in the client). We have a protocol level flag stating we are an interactive client so this could be used to do it.

tags: added: low-hanging-fruit
Olaf van der Spek (olafvdspek) wrote :

> or receive the blob and convert it to human-readable in the client

This looks like the better approach.

Hello,

I am completely new to drizzle. Can anyone give me some pointers on this bug. How can I reproduce this bug? So I can get a better understanding. Thanks.

Nishank Bisht <email address hidden> writes:
> I am completely new to drizzle. Can anyone give me some pointers on this
> bug. How can I reproduce this bug? So I can get a better understanding.
> Thanks.

It'll be in client/drizzle.cc and related files. When you have a blob
column in a table and you SELECT from it from the drizzle command line
client, you'll get the contents of that blob just printed to the screen,
inculding any unprintable characters. The idea is to print it out like
how you would insert such values - escaping them.

have a follow through of what the command line client does when you run
a query, setting some breakpoints along the way. You should be able to
find the bit where it works out the type of the column being received
and decides how to display it.

--
Stewart Smith

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers