Support Table Type Columns
It appears that Schema Compare does not support table types as columns. I have a table that had a type type added to it on dev. I compared it with QA and it correctly detected the difference, however, the migration script did not include the storage clause necessary for deployment. The statement it created is this:
ALTER TABLE xxproduct.auditlog ADD (auditvalue xxproduct.auditvaluetab);
It should have created something along these lines:
ALTER TABLE xxproduct.auditlog ADD (auditvalue xxproduct.auditvaluetab)
NESTED TABLE "AUDITVALUE" STORE AS "AUDITVALUES"
(PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 LOGGING
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1
BUFFERPOOL DEFAULT FLASHCACHE DEFAULT CELLFLASHCACHE DEFAULT)
TABLESPACE "XXTSTX_DATA" ) RETURN AS VALUE;
I’ve been working on this lately as although it could create a new table the migration scripts were very broken.
Let me know if you want a pre-release version to try the fix out.
This will included in the next release of the tools.
-
Anonymous commented
I haven't tried the "Ignore Storage" setting. I don't actually need all the storage information, just the nested table information. Not ignoring the storage may actually cause a lot more differences than I care about.
-
Anonymous commented
Thank you for the offer, but no, I'll wait for the normal release.
-
AdminRichard Mitchell (Admin, Redgate) commented
Have you tried with the "Ignore Storage" setting turned off? This will include a lot of the extra storage options that you're indicating here.
I've been playing with nested tables recently to fix some issues in Data Compare for Oracle.