DB2 some binary fields not properly formatted since 6.3.5

Since version 6.3.5 (including 7.x) columns that are defined as datatype CHAR(13) FOR BIT DATA no longer get formatted according to the Binary data formatter setting (global or connection specific). All 6.3.x versions prior to 6.3.5 work as expected.

System information:

• Linux / Mac
• DBeaver v6.3.5 or greater
• DB2 LUW driver with default settings

The following examples are with the binary data formatter set to Hex formatting.

Both columns displayed the same values prior to 6.3.5. But that version or higher show garbled text instead of hex formatting the binary value.

SELECT mycolumn AS the_column, hex(mycolumn) AS the_column_cast_as_hex FROM mytable LIMIT 5;

Result in version 6.3.4

Result in 6.3.5

[gsaulmon]

Full reproduction steps.

Tested on 7.0.2

Optional: setup a db2 server

This will create a db2 server that you can connect to at localhost with a database of testdb, username of db2inst1 and password of test

docker run -it --rm --name db2 --cap-add IPC_LOCK --cap-add IPC_OWNER -p 50000:50000 -e LICENSE=accept -e DB2INST1_PASSWORD=test -e DBNAME=testdb ibmcom/db2

Create a DB2 LUW connection to the db2 instance

• Edit the connection and set Result Sets -> Editors -> Binary data formatter to Hex

Create some data

CREATE SCHEMA "MYTEST";
CREATE TABLE "MYTEST"."MYTABLE" ( "MYFIELD" CHAR(13) FOR BIT DATA NOT NULL );
INSERT INTO mytest.MYTABLE  (MYFIELD) VALUES (generate_unique()), (generate_unique());

Query it

SELECT myfield, hex(myfield) AS myfield_as_hex FROM mytest.mytable;

That query will return with both columns matching and properly formatted as hex; only until you disconnect the first time.

Once you’ve disconnected/reconnected or closed/reopened dbeaver the formatting is no longer applied to the results of that query.

It should also be noted that creating temporary binary data in a query is always formatted correctly. Results from SELECT generate_unique() FROM SYSIBM.sysdummy1; are formatted correctly

[kseniiaguzeeva]

verified