Re: Why store nested tables or varrays in a column?
Date: Tue, 17 Nov 2009 07:09:37 -0800 (PST)
On Nov 16, 7:27 pm, "phil_herr..._at_yahoo.com.au" <phil_herr..._at_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 objectrelational object types to learn when and where the objects can be used effectively.
HTH -- Mark D Powell -- Received on Tue Nov 17 2009 - 09:09:37 CST