[GH-ISSUE #383] Cannot update PostgreSQL updatable view #109

New issue

Open

opened 2026-03-07 20:44:56 +03:00 by kerem · 4 comments

kerem commented

2026-03-07 20:44:56 +03:00

Owner

Originally created by @ajkq on GitHub (Jun 3, 2021).
Original GitHub issue: https://github.com/dbeaver/cloudbeaver/issues/383

Describe the bug
A PostgreSQL updatable view cannot be updated. Error message:
Can't detect row identifier for data container 'v_test'. It must have at least one unique key.

To Reproduce
Steps to reproduce the behavior:
1.

CREATE SCHEMA test;
CREATE TABLE test.test (
	id integer PRIMARY KEY,
	value integer NULL
);
CREATE VIEW test.v_test
AS SELECT test.id, test.value
FROM test.test;
INSERT INTO test.v_test (id, value) VALUES(1, NULL);

Try to change value

Desktop:

OS: macOS 11.4
Browser Chrome
Version 91

Additional context
Database: PostgreSQL 13.3

Originally created by @ajkq on GitHub (Jun 3, 2021). Original GitHub issue: https://github.com/dbeaver/cloudbeaver/issues/383 **Describe the bug** A PostgreSQL updatable view cannot be updated. Error message: `Can't detect row identifier for data container 'v_test'. It must have at least one unique key.` **To Reproduce** Steps to reproduce the behavior: 1. ``` CREATE SCHEMA test; CREATE TABLE test.test ( id integer PRIMARY KEY, value integer NULL ); CREATE VIEW test.v_test AS SELECT test.id, test.value FROM test.test; INSERT INTO test.v_test (id, value) VALUES(1, NULL); ``` 2. Try to change value **Desktop:** - OS: macOS 11.4 - Browser Chrome - Version 91 **Additional context** Database: PostgreSQL 13.3

kerem added the

xf:data editor

label

2026-03-07 20:44:56 +03:00

kerem commented

2026-03-07 20:44:57 +03:00

Author

Owner

@kseniiaguzeeva commented on GitHub (Jun 9, 2021):

Thank you for the report. We will add this option.

@kseniiaguzeeva commented on GitHub (Jun 9, 2021): Thank you for the report. We will add this option.

kerem commented

2026-03-07 20:44:57 +03:00

Author

Owner

@serge-rider commented on GitHub (Jul 6, 2021):

It requires a complicated UI to define virtual unique key.

We have such a feature in the desktop product.

@serge-rider commented on GitHub (Jul 6, 2021): It requires a complicated UI to define virtual unique key. We have such a feature in the desktop product.

kerem commented

2026-03-07 20:44:57 +03:00

Author

Owner

@ajkq commented on GitHub (Jul 9, 2021):

Adminer uses all columns in the where clause. Would that be an option?

@ajkq commented on GitHub (Jul 9, 2021): Adminer uses all columns in the where clause. Would that be an option?

kerem commented

2026-03-07 20:44:57 +03:00

Author

Owner

@kseniiaguzeeva commented on GitHub (Jul 9, 2021):

Thank you for your idea. A lot of UI changes must be done to implement the feature by the best way. An option to use all columns as a unique key can make work with tables inconvenient in some cases.

@kseniiaguzeeva commented on GitHub (Jul 9, 2021): Thank you for your idea. A lot of UI changes must be done to implement the feature by the best way. An option to use all columns as a unique key can make work with tables inconvenient in some cases.

kerem referenced this issue

2026-03-07 21:04:05 +03:00

[PR #109] [MERGED] refactor: data management behavior #1457