Editing column data in UI does not work when primary key is uuid

System information:

• Operating system (distribution) and version: Windows 10
• DBeaver version: 7.2.2.202010041557

Connection specification:

• Database name and verison: Postgres (tested on 9.6 and 11)
• Driver name: PostgreSQL JDBC Driver
• Do you use tunnels or proxies (SSH, SOCKS, etc): No

Describe the problem you’re observing:

When editing the value of a cell, pressing “Save” will give the error Object parameter [4e3f75d2-3375-4040-9c02-3a8c15a8be87] binding not supported where 4e3f75d2-3375-4040-9c02-3a8c15a8be87 is the value of the primary key column. The primary key column is of type uuid. The type of the edited cell it self does not seem to matter (tested with text, int and jsonb). Doing the same on a table with primary key of type int, works fine.

Steps to reproduce, if exist:

CREATE TABLE test (
  id uuid,
  name text,
  PRIMARY KEY (id)
);

INSERT INTO test 
  VALUES 
    ('72644fac-9e7b-4da3-b801-ba80c1bb4fd5', 'test 1'), 
    ('6b24f99a-4c58-4bac-92c3-5a756281d431', 'test 2');

SELECT * FROM test;

Mark one of the name cells and press shift+enter to open the editor.

Change the value and press “Save”

Press “Save” in the bottom left (or ctrl+s).

Gives this error:

If I do the same with a table that has an int primary key column (instead of a uuid), it works just fine.

Include any warning/errors/backtraces from the logs

!ENTRY org.jkiss.dbeaver.model 4 0 2020-10-05 08:58:29.382 !MESSAGE Object parameter [6b24f99a-4c58-4bac-92c3-5a756281d431] binding not supported !SUBENTRY 1 org.jkiss.dbeaver.model 4 0 2020-10-05 08:58:29.382 !MESSAGE Object parameter [6b24f99a-4c58-4bac-92c3-5a756281d431] binding not supported !STACK 0 org.jkiss.dbeaver.model.exec.DBCException: Object parameter [6b24f99a-4c58-4bac-92c3-5a756281d431] binding not supported at org.jkiss.dbeaver.model.impl.data.DefaultValueHandler.bindValueObject(DefaultValueHandler.java:60) at org.jkiss.dbeaver.model.impl.jdbc.struct.JDBCTable$2.bindStatement(JDBCTable.java:466) at org.jkiss.dbeaver.model.impl.data.ExecuteBatchImpl.processBatch(ExecuteBatchImpl.java:156) at org.jkiss.dbeaver.model.impl.data.ExecuteBatchImpl.execute(ExecuteBatchImpl.java:77) at org.jkiss.dbeaver.ui.controls.resultset.ResultSetPersister$DataUpdaterJob.executeStatements(ResultSetPersister.java:804) at org.jkiss.dbeaver.ui.controls.resultset.ResultSetPersister$DataUpdaterJob.lambda$1(ResultSetPersister.java:690) at org.jkiss.dbeaver.model.exec.DBExecUtils.tryExecuteRecover(DBExecUtils.java:168) at org.jkiss.dbeaver.ui.controls.resultset.ResultSetPersister$DataUpdaterJob.executeStatements(ResultSetPersister.java:689) at org.jkiss.dbeaver.ui.controls.resultset.ResultSetPersister$DataUpdaterJob.run(ResultSetPersister.java:627) at org.jkiss.dbeaver.model.runtime.AbstractJob.run(AbstractJob.java:105) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)

[rafaelrpinto]

Folks, please click on the 👍 reaction button of the issue instead of creating a new +1 comment so people subscribed to this thread waiting for an actual update on the issue don’t receive 10 useless emails a day until the next version is released. Thank you.

[mortifia]

7.2.3 doesn’t patch this bug @serge-rider