Compare user objects - there is still something to be done

[paweld]

Hello! Thank you all in Allround Automations very much for eliminating errors in compare mechanism mentioned e.g. here . However it wasn't difficult to produce next example where compare function fails. Below three different examples which are identical according to "Compare user objects" function.

Support info from my PC

PL/SQL Developer
  Version 7.0.2.1076 (MBCS)
  97.33630 - 20 user license
  Windows XP version 6,0 (build 2600) Dodatek Service Pack 2

Using
  Home: OraHome92
  DLL: C:\oracle\ora92\bin\oci.dll
  OCI: version 9.2
  Oracle9i Enterprise Edition Release 9.2.0.7.0
  Character size: 1 byte(s)

Testcase 1

connect sys/change_on_install@targetdb as sysdba
drop user zijtesi cascade
/
create user zijtesi identified by zijtesi
/
grant connect, dba to zijtesi
/
create table zijtesi.test_drop_col (
  col_1 number(1),
  col_2 number(4),
  col_2a number(4)
  )
/
connect sys/change_on_install@sourcedb as sysdba
drop user zijtesi cascade
/
create user zijtesi identified by zijtesi
/
grant connect, dba to zijtesi
/
create table zijtesi.test_drop_col (
  col_1 number(1),
  col_2 number(4),
  col_2a number(4)
  )
/
alter table zijtesi.test_drop_col drop column col_2
/
alter table zijtesi.test_drop_col rename column col_2a to new_column
/

Testcase 2

connect sys/change_on_install@targetdb as sysdba
drop user zijtesi cascade
/
create user zijtesi identified by zijtesi
/
grant connect, dba to zijtesi
/
create table zijtesi.test_drop_col (
  col_1 number(1),
  col_2 number(4),
  col_2a number(4)
  )
/
connect sys/change_on_install@sourcedb as sysdba
drop user zijtesi cascade
/
create user zijtesi identified by zijtesi
/
grant connect, dba to zijtesi
/
create table zijtesi.test_drop_col (
  col_1 number(1),
  col_2 number(4),
  col_2a number(4)
  )
/
alter table zijtesi.test_drop_col rename column col_2 to new_column
/
alter table zijtesi.test_drop_col drop column col_2a
/

Testcase 3

connect sys/change_on_install@targetdb as sysdba
drop user zijtesi cascade
/
create user zijtesi identified by zijtesi
/
grant connect, dba to zijtesi
/
create table zijtesi.test_drop_col (
  col_1 number(1),
  col_2 number(4),
  col_2a number(4)
  )
/
connect sys/change_on_install@sourcedb as sysdba
drop user zijtesi cascade
/
create user zijtesi identified by zijtesi
/
grant connect, dba to zijtesi
/
create table zijtesi.test_drop_col (
  col_1 number(1),
  col_2 number(4),
  col_2a number(4)
  )
/
alter table zijtesi.test_drop_col drop column col_2
/
alter table zijtesi.test_drop_col drop column col_2a
/
alter table zijtesi.test_drop_col add (new_column number(4))
/

In every one of the three cases I've got the same result which follows

rem Differences between ZIJTESI@SOURCEDB and ZIJTESI@TARGETDB, created on 2006-05-23
rem Press Apply button, or run in Command Window or SQL*Plus connected as ZIJTESI@TARGETDB

-----------------------------------
--  Changed table test_drop_col  --
-----------------------------------
-- Drop columns
alter table TEST_DROP_COL drop column COL_2A;
alter table TEST_DROP_COL rename column COL_2 to NEW_COLUMN;

rem Differences between ZIJTESI@SOURCEDB and ZIJTESI@TARGETDB, created on 2006-05-23
rem Press Apply button, or run in Command Window or SQL*Plus connected as ZIJTESI@TARGETDB

 

[Marco Kalter]

We'll check it out.