Need options for restricting system generated objects from being compared in Toad schema comparison (4334489)

Let's see this better with an example:

Let's assume there are two schemes: schema1 and schema2 and the table below exists in both of them

CREATE TABLE test_table
(
id NUMBER GENERATED ALWAYS AS IDENTITY,
name VARCHAR2 (100)
);

the script in both if them is

CREATE TABLE TEST_TABLE
(
ID NUMBER Generated as Identity ( START WITH 1 MAXVALUE 9999999999999999999999999999 MINVALUE 1 NOCYCLE CACHE 20 NOORDER NOKEEP) NOT NULL,
NAME VARCHAR2(100 BYTE)
)
TABLESPACE USERS

Enter a value into the table in schema1:

INSERT INTO test_table (name)
VALUES ('a');

commit;

the script on schema1 changes to

CREATE TABLE TEST_TABLE
(
ID NUMBER Generated as Identity ( START WITH 21 MAXVALUE 9999999999999999999999999999 MINVALUE 1 NOCYCLE CACHE 20 NOORDER NOKEEP) NOT NULL,
NAME VARCHAR2(100 BYTE)
)
TABLESPACE USERS

note that the star with value has changed.

If you run a schema compare between the 2 schemes, you will get that these tables are different and you will get an alter statement for this difference.

Would it be possible to have an option to ignore this modification?

WORKAROUND

STATUS

Issue fixed in version 12.9. The latest version of Toad for Oracle can be downloaded at: https://support.quest.com/toad-for-oracle/download-new-releases