Marco,
the "Checks" tab in "view table" window displays no constraints.
at the same time the "check" constraints are displayed in the "object browser".
I think it is a pretty severe bug, unless i'm missing smth.
CONSTRAINT_NAME CONSTRAINT_TYPE TABLE_NAME
SYS_C0080418 C CLASS_00
SYS_C0080419 C CLASS_00
SYS_C0080420 C CLASS_00
CLASS_00_PKEY P CLASS_00
CLASS_00_DEAL_ID_FK R CLASS_00
not sure how to attach the screenshot, but in the window i see non for type "C". The PK and FK are in place ( but it's a different tab).
Please advise.
Perhaps these are "not null" constraints, and are displayed as such at the column level?
indeed they are Marco.
But why would they be displayed somewhere else, not with all other C-constraints in that tab?
when you said "displayed @ column level". did you mean in the "columns" tab?
If so, then i would argue that there are no names (for constraints) displayed in the (columns) tab.
Let me know, please
Yes, they are displayed as not nullable on the columns tab page. The names you are seeing in the constraints view are system generated, and have no meaning.
I would argue against "have no meaning" - strictly speaking all names have no meaning - just a place holders for humans. BUT from consistency standpoint - there should be no distinguish between system generated and manually entered names.
What's the benefit of having this exclusion?
The benefit is that is easier to interpret the fact that a column is not nullable than that it has a constraint named SYS_C0080418.
Do you think if you populate the columns in the tab ( "Condition","Enabled" etc) it will be sufficient for user to quickly identify such a case?
For example in the "Indexes" tab the software does display the system generated indexes, correct?
this is how SQLDeveloper( Oracle Corp) has it:
SYS_C0023209 Check "APPRAIS_TYP_KEY" IS NOT NULL ENABLED NOT DEFERRABLE VALIDATED GENERATED NAME 22-JAN-11
SYS_C0023210 Primary_Key ENABLED NOT DEFERRABLE VALIDATED GENERATED NAME 22-JAN-11 SFDISB SYS_C0023210
and this is perfect - i see all info and there is no ambiguity and i don't have to click anywhere else to figure out what else might be for "constraints".
there is another problem with the current approach - since the SYS_ names are not displayed ( on the tab) it's easy to overlook during the review. If i need to rename sys generated to more human friendly.
Another problem (bug) is with the "edit" functionality:
object browser -> tables ( pick one with check constraint) -> check constraints -> (pick one and expend it). Right click on the name and select "Edit" from the drop-down. The "edit table" menu opens up. BUT since this constraint is not in the tab you can't modify it.