Re: Why store nested tables or varrays in a column?
From: <phil_herring_at_yahoo.com.au>
Date: Mon, 16 Nov 2009 16:27:02 -0800 (PST)
Message-ID: <4d754951-d66f-425d-96e2-32ade3eb0406_at_j9g2000prh.googlegroups.com>
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.
Date: Mon, 16 Nov 2009 16:27:02 -0800 (PST)
Message-ID: <4d754951-d66f-425d-96e2-32ade3eb0406_at_j9g2000prh.googlegroups.com>
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