The document discusses Oracle's claim of being a 100% relational database management system (RDBMS). It raises three key points:
1) Oracle uses sequence objects to generate unique IDs for entities, but sequence values can be shared across multiple entities, similar to picking a value from another table.
2) Sequence objects support a recycle feature, meaning the same value can be used multiple times internally.
3) Without the DBA_SEQUENCES object, Oracle does not natively support primary keys except by programmatically incrementing values.
The document calls for feedback on Oracle's authenticity as a 100% RDBMS.
3. Curtain-Raiser Here, I would like to have an Open ended discussion with Objective approach to find answers to following Questions… a)Authenticity of Oracle’s 100% RDBMS
4. a)Authenticity of Oracle’s 100% RDBMS Sequence Object Usage: To Generate the value unique id for an instance of entity, Oracle uses the sequence Object.. Well, so far ..so good.. But, sequence object values can be shared across multiple entities, Which is as good (worse) as picking a value from another table (call it… dba_sequences) for using it as PK value …
5. a)Continued... TO MAKE THINGS WORSEN, Sequence object supports recycle-feature… It means, internally, a sequence instance may have same value multiple times. Oh, GOD ONLY CAN SAVE ME FROM DESIGNING MODELIN ORACLE……? So, In the absence of DBA_SEQUENCES Object, Oracle does not have the support for PK value EXCEPT INCREMENTING THE VALUE PROGRAMMATICALLY..
