Oracle_Objects + Evolution = Impossible!

When are Oracle going to address the stupidity in their objects modelling, in that you cannot evolve objects used in object relational databases; and they have extremely limited functionality? Please don't suggest Java, as a rewrite on existing ORDBs is impractical.

Want to add a new attribute...tough!
Want to change an attribute's type...tough! Want to change an object's member procedure or function parameters...tough!
Want a nested collection within a nested collection...tough! Want to have a privately scoped member procedure or function...tough! Want to declare an attribute type of MYTABLE.MYFIELD%TYPE...tough! Want to declare an object inherited from another object...tough! Want polymorphism...tough!

This is the most ridiculous situation they have ever created. What do they suggest to people who need to change an object used in an existing ORDB?

Paul Received on Wed Feb 16 2000 - 00:00:00 CST