Product: Aqua Data Studio
Version: 16.0.1-4
Build #: 43080
Build Date: 2015-Mar-23 01:31:06 PM
Operating Environment: Linux (3.13.0-32-generic, amd64) / UTF-8 / en / IN / Oracle Corporation 1.7.0_60-b19
Memory: Max=704,643,072; Total=286,261,248; Free=174,793,384; CPUs=8
Steps to reproduce:
1.Connect to PostgreSQL 9.3.
2.Create a table in 'public' schema:
CREATE TABLE public."binary_datatype" (
"bytea_col" bytea NULL
)
go
3. Insert values in it.
INSERT INTO public."binary_datatype"("bytea_col")
VALUES('4a')
GO
4. Run SELECT* query on it.
SELECT * FROM public."binary_datatype"
GO
5.Result displayed is not the value which we have inserted.
Result displayed as :
3461
But when we perform above steps in pgAdmin III native Tool result is same value which we have inserted through insert command (i.e 4a).
If we are converting given input , please explain the conversion.
Observation : This behavior is also observed in ADS 15.0.15.
|
147 KB
How binary data is displayed is controlled by the "convert binary to hex" option in File -> Options -> Results.
If the "convert binary to hex" option is checked, the data will be displayed as "3461".
If the "convert binary to hex" option is unchecked, the data will be displayed as "4a".
Issue #13174 |
Closed |
Fixed |
Resolved |
Completion |
No due date |
No fixed build |
No time estimate |
How binary data is displayed is controlled by the "convert binary to hex" option in File -> Options -> Results.
If the "convert binary to hex" option is checked, the data will be displayed as "3461".
If the "convert binary to hex" option is unchecked, the data will be displayed as "4a".