Did some research (and tried it myself) and this is what I understand from
object tables (or tables that have one if its fields being an object type)
in 9i.... In order to make a change later on to the object, any table that
is using it (wheter it is one field or an object table) would first have to
be dropped. Otherwise it gives dependency errors. Is this correct? This
doesn't make sense to me... How can it be expected that an object can never
later be changed (adding another field, increasing a varchar2 field, etc).
This makes them "useless" to me to want to use an object in a table.
-
Replace nospam with hotmail for e-mail.
Received on Tue Jul 06 2004 - 18:33:22 CDT
