Hex tab of Grid Popup editor shows 2-byte characters

Toad for Oracle
1

I have notoiced that Hex tab of TOAD Grid Popup editor (the one that opens when you double-click on a field in Schema Browser) shows 2-byte characters when in fact the data contains only single-byte characters; the second byte displayed is always 00. For a fixed-length field, like CHAR(14 BYTE), the Hex tab shows 28 bytes - 14 bytes with real values, each followed by byte 00. I have checked by querying DUMP() of the filed, and it reports the length of field is really 14 bytes, and lists all characters in it.

My database is Oracle 11.2, with character set WE8MSWIN1252, which, I believe, cannot store 2-byte characters even if I tried.

Attached is a screenshot of the Hex tab that shows content of a CHAR(14 BYTE) field; the field contains 7 digits padded by 7 spaces, but TOAD displays 2-byte characters, and 28 bytes as the field length.

Something wrong with how TOAD displays the data in Hex tab, showing extra bytes that do not really exist?

Hex_tab.jpeg
Hex_tab.jpeg1008×630 50.2 KB

2

The Hex tab has become increasingly less useful. All strings are stored as UTF-16 internally within Toad. The Hex tab shows the hex representation of the string
as stored in Toad, not the data as stored in your database. To get accurate representation of your data you should use Oracle’s DUMP function or something similar.

Michael

From: bosh8 [mailto:bounce-bosh8@toadworld.com]

Sent: Wednesday, May 13, 2015 10:26 AM

To: toadoracle@toadworld.com

Subject: [Toad for Oracle - Discussion Forum] Hex tab of Grid Popup editor shows 2-byte characters

Hex tab of Grid Popup editor shows 2-byte characters

Thread created by bosh8

I have notoiced that Hex tab of TOAD Grid Popup editor (the one that opens when you double-click on a field in Schema Browser) shows 2-byte characters when in fact
the data contains only single-byte characters; the second byte displayed is always 00. For a fixed-length field, like CHAR(14 BYTE), the Hex tab shows 28 bytes - 14 bytes with real values, each followed by byte 00. I have checked by querying DUMP() of the
filed, and it reports the length of field is really 14 bytes, and lists all characters in it.

My database is Oracle 11.2, with character set WE8MSWIN1252, which, I believe, cannot store 2-byte characters even if I tried.

Attached is a screenshot of the Hex tab that shows content of a CHAR(14 BYTE) field; the field contains 7 digits padded by 7 spaces, but TOAD displays 2-byte characters,
and 28 bytes as the field length.

Something wrong with how TOAD displays the data in Hex tab, showing extra bytes that do not really exist?

Attachments:

Hex_tab.jpg

To reply, please reply-all to this email.

Stop receiving emails on this subject.

Or
Unsubscribe from Toad for Oracle - General notifications altogether.

Toad for Oracle - Discussion Forum

Flag
this post as spam/abuse.