CREATE TABLE "NEO"."TB_RAW"
( "PURPOSE" VARCHAR2(128 BYTE) NOT NULL ENABLE,
"BYTES" RAW(2000) INVISIBLE NOT NULL ENABLE
);
Windows 11.
Open the table from the tree view. In the Columns section, the table attributes are displayed, including the column names of invisible column. The column attributes do not have an INVISIBLE attribute shown. It is inconsistent to expose the column name but not indicate that it is invisible.
In the Data section, existing rows are displayed, absent is the invisible “BYTES” column. Only the "PURPOSE" column is shown.
The + INSERT action is enabled. You can enter data for the "PURPOSE" column ONLY. Why is + INSERT enabled when data cannot be saved**?**
A improved user experience would be to add a UI element such as a checkbox which exposes INVISIBLE columns
[x] “Show invisible columns”;
Or, disable the +INSERT action,
Or, a show a pop-up message informing what's going on.
Clicking + INSERT permits the editing dialog allowing data entry for the visible column only. The INVISIBLE column is not available for input. SQLDEV does not store the newly entered data into the new row which you're attempting to insert. Assume that this is intentional to avoid NOT NULL constraint exception of invisible column. SQLDEV disables the other clickable actions (Delete Selected, Commit, Undo All). The user experience is somewhat clumsy as the UI is not obvious. SQLDEV does not give any feedback about this scenario aside from disabling actions). The entered data is not captured, instead SQLDEV stores (null) into the new row / column instead of the entered data.
Aas of now it's a waste of one's time to perform the data entry steps and not know the actual reason why data cannot be saved when unaware of the INVISIBLE column.
Is this scenario hinted at in the SQLDEV user guide?