Not Null indicator in UI is incorrect

[muskyhippo]

Description

• When adding a Not Null check constraint with a custom name, the Not Null condition is not checked in the Not Null column of the columns tab in the Database Object Editor, Properties tab in the UI.
• If adding a Not Null check constraint, letting the system generate the name, it works correctly.

DBeaver Version

Version 25.0.1.202503231807

Operating System

Windows 11 Pro Version 10.0.26100 Build 26100

Database and driver

Oracle 19.0.0.0.0
oracle.jdbc.OracleDriver

Steps to reproduce

In an SQL window run the following:
CREATE TABLE test_named_cc
(id NUMBER
,text varchar2(10)
,value varchar2(10)
,CONSTRAINT test_named_cc__id_nn_cc CHECK (id IS NOT NULL)
,CONSTRAINT test_named_cc__text_nn_cc CHECK (text IS NOT NULL)
);

Now look at the table in the Database Object Editor.
Navigate to the Properties tab and then the Columns tab.
The Not Null column is incorrectly blank for the "ID" and "TEXT" columns.

If the same process is done, but without a custom name for the check constraint, it works correctly.
In an SQL window run the following:
CREATE TABLE test_auto_cc
(id NUMBER NOT NULL
,text varchar2(10) NOT NULL
,value varchar2(10)
);

Additional context

No response

[IvanGorshechnikov]

Hello @bkyle

It works as expected. Defining not null via a constraint and as a column parameter are different mechanisms, and they are displayed in different places.

In the properties window, columns are set to the not null value defined for that column. Formally, when not null is defined by constraint, the column is nullable (unless otherwise specified). To see your constraints, you can open the appropriate tab and see all the constraints for a given table, including not null.