Hello,

What is the ability to store nested tables and varrays in a column
used for?  It seems like this would be counter to the concept of
normalization.  I just can't think of a good use.

Thanks.

It's a fossil of fashions past. A number of years ago there was a fad
for object-oriented everything. When it reached Oracle, they decided
to add objects to tables, so they could say they're O-O, too. Not many
people use the feature; occasionally someone decides it's a great idea
and they try to use it, but they usually only do that once.

Mind you, it does get used a a few specialised areas. I can't imagine
Spatial being very usable without it.


-- Phil

On Nov 16, 7:27=A0pm, "phil_herr...@yahoo.com.au"
<phil_herr...@yahoo.com.au> wrote:
> It's a fossil of fashions past. A number of years ago there was a fad
> for object-oriented everything. When it reached Oracle, they decided
> to add objects to tables, so they could say they're O-O, too. Not many
> people use the feature; occasionally someone decides it's a great idea
> and they try to use it, but they usually only do that once.
>
> Mind you, it does get used a a few specialised areas. I can't imagine
> Spatial being very usable without it.
>
> -- Phil

Jake, using nested tables is counter to the normal rules of
normalization, namely no repeating groups.  There are however
applications where nested tables may be effectively used.  In most
cases you can build your nested objects in the application layer and
not store the data permanently using nested tables.

You asked a good question; it takes time and study of the object-
relational object types to learn when and where the objects can be
used effectively.

HTH -- Mark D Powell --