it lets people know that that 'thing' is about to go away and they should start thinking about using something else instead
I cannot find any reference to this in the help system or docs. It shows as a check box for entities attributes and tables. What is the intended use and implication of using it?
Yet there are PLENTY of references and definitions of 'deprecated' on the web.
In several fields, deprecation is the discouragement of use of some terminology, feature, design, or practice; typically because it has been superseded or is no longer considered efficient or safe – but without completely removing it or prohibiting its use.
This chapter describes behavior changes where features have been deprecated or desupported in this release. By deprecate, we mean that the feature is no longer being enhanced but is still supported for the full life of the 12.1 release. By desupported, we mean that Oracle will no longer fix bugs related to that feature and may remove the code altogether. Where indicated, a deprecated feature may be desupported in a future major release. For more information about support considerations, refer to My Oracle Support at
Were you concerned that it meant something else?
Yes, clearly I am able to read definitions on the web and fully understand what deprecated means in theory.
My question was quite precise and went unanswered.
There is a deprecated check box available for entities, attributes and tables. There is nothing in the product docs to indicate what is the implication of using it. For example, do deprecated entities and attributes no longer get engineered forward to a relational model or do deprecated tables not generate DDL? Or, as it seems from the obvious answers I got, it means nothing at all - it is simply "documentation" and does not effect the outcome of the generators or reports. I do notice a strike through appears through the text.
By way of "asking for implication", defined as " implied
It seems like it is documentation only.
I am also alerting the product team that there are settings in Sql Developer Data modeler that are not documented in the product.
thank you that's what I was looking for - it's documentation only.
see how easy that was?
and why is this no in the docs?
It' probably assumed to be self-explanatory, or it's an oversight.