How to compare content in different versions of case?

Question

Need to compare attributes of tables, columns, sequences etc between case115 and case121. Think I should be able to use views like ci_table_definitions to do that so tried setting up an account that dblinks to the different case dbs. Problem seems to be that I get duplicate rows retrieved from those views. If I sqlplus directly into case115
and run exec jr_context.set_workarea('GLOBAL SHARED WORKAREA') it seems to setup session so the view gives single row. So is there some sql to add to a query running from my dev account that would achieve the same filter? Alternativly is the source for jr_context available so I can build that in dev account? Any better ideas?
Thanks , Aidan

Answer 1

Thanks John, I'll look into that approach. This repository is shared by 100s of developers across multiple products so I'm not sure what licence I have to do much in the repository itself. Also although case115 is older version its still being updated - the requirement is not exactly to sync 4 different codelines as new features are added in later codelines but need to do comparisons to verify all essential updates have been made in different levels of schema.
Still be interested if anyone has a method of implementing the filter to avoid duplicate rows retrieved from these views. Currently just using a very basic rownum filter to avoid cartesian:
select ' '
,decode(case115.AUTO_GENERATED,case121.AUTO_GENERATED, null, 'CI_COLUMNS|'||case115_td.name||' | '||case115.name||' | AUTO_GENERATED | case115 | '||case115.AUTO_GENERATED||' | <> case121 | '||case121.AUTO_GENERATED)
,decode(case115.AVERAGE_LENGTH,case121.AVERAGE_LENGTH, null, 'CI_COLUMNS|'||case115_td.name||' | '||case115.name||' | AVERAGE_LENGTH | case115 | '||case115.AVERAGE_LENGTH||' | <> case121 | '||case121.AVERAGE_LENGTH)
.... generated select for all columns in a ci view
from
( select CC.rowid col_rowid, CC.NAME col_name, CC.ivid col_ivid,
CTD.ID ID, CTD.IVID IVID, CTD.NAME NAME, CTD.ALIAS ALIAS,
CTD.USER_DEFINED_PROPERTY_18 USER_DEFINED_PROPERTY_18
from CASE115_TABLE_DEFINITIONS CTD, CASE115_COLUMNS CC
where CTD.name like upper('&table%')
and cc.TABLE_REFERENCE = CTD.id
and cc.rowid = ( select cc_2.rowid from CASE115_COLUMNS cc_2
where cc_2.ID = cc.ID
and rownum = 1)
and CTD.rowid = ( select case115_TD_2.rowid from CASE115_TABLE_DEFINITIONS case115_TD_2
where case115_TD_2.ID = CTD.ID and ROWNUM = 1)) CASE115_TD,
( select CC.rowid col_rowid, CC.NAME col_name, CC.ivid col_ivid,
CTD.ID ID, CTD.IVID IVID, CTD.NAME NAME, CTD.ALIAS ALIAS,
CTD.USER_DEFINED_PROPERTY_18 USER_DEFINED_PROPERTY_18
from CASE121_TABLE_DEFINITIONS CTD, CASE121_COLUMNS CC
where CTD.name like upper('&table%')
and cc.TABLE_REFERENCE = CTD.id
and cc.rowid = ( select cc_2.rowid from CASE121_COLUMNS cc_2
where cc_2.ID = cc.ID
and rownum = 1)
and CTD.rowid = ( select case121_TD_2.rowid from CASE121_TABLE_DEFINITIONS case121_TD_2
where case121_TD_2.ID = CTD.ID and ROWNUM = 1)) CASE121_TD,
CASE115_COLUMNS case115, CASE121_COLUMNS case121
where CASE115.rowid = CASE115_TD.col_rowid
and CASE121.rowid = CASE121_TD.col_rowid
and case115_TD.name = case121_TD.name(+)
and case115_TD.col_name = case121_TD.col_name(+)
ORDER BY CASE115_TD.name, CASE115.order_sequence, CASE115_TD.col_name
So this works from a dev db that dblinks to 4 case repository dbs. Sql generates lots of blank lines that are stripped out. Its pretty slow! So be useful to replace the rownum filter with equivelent of jr_context.set_workarea('GLOBAL SHARED WORKAREA')
Regards, Aidan