Comments
Sort by recent activity
Thanks for your reply.
I'm using 3.1.5.1321, trial version. / comments
Thanks for your reply.
I'm using 3.1.5.1321, trial version.
We have 'solved' this by overriding two views in our development databases before we run schema compare. We add these views to the schema.
The first view is basically to tell Schema Compare to never mind the dependencies, and the second view is to prevent our overrides from showing up in the comparison. create or replace view DBA_DEPENDENCIES as
select *
from ALL_DEPENDENCIES
where 1=0;
create or replace view DBA_VIEWS as
select *
from ALL_VIEWS
where VIEW_NAME not in ('DBA_VIEWS', 'DBA_DEPENDENCIES');
This makes the process of comparing a LOT faster, and it's good enough for storing changes in a Git working folder. It may however affect the order of changes in generated release scripts, so we must take care in reviewing this ourselves or at least recompiling invalid objects after a release. Getting everthing is Git was the top priority for us anyway, and this change makes the tool at least usable to us, although we'd like to see an actual feature so we can eliminate the hack. / comments
We have 'solved' this by overriding two views in our development databases before we run schema compare. We add these views to the schema.
The first view is basically to tell Schema Compare to neve...