Maxmix
Member³
Every day I'm suffering from one missing feature.
Namely, I want (many times a day) to be able to instantly compare a particular VIEW's definition across databases. Of course, there are many other types of objects, comparison of which is not trivial with PLSQL Developer (grants, roles, db links etc), but Views... views are special, we are changing them constantly.
"Normal" way would be to utilize 'Compare User Objects' but it requires the tedious setup.
The context menu's command 'Compare to Other database source' is not available for VIEWs, only for PL/SQL modules.
If only I could right-click on view name, choose 'Compare to Other database source' and... something good would happen.
For example, process could be similar to the one for PLSQL program modules:
1. prompt pops up to establish connection to 'other side'
2. immediately after successful connection ExamDiff launches with ready comparison results.
Another implementation is probably feasible only after a good tuning of 'CompareUserObjects' module:
1. I am right-clicking on a VIEW (or any other object type) name,
2. choose 'Compare...'
3. I am presented with CompareUserObjects window, prepared to comparison (i.e., only one selected object comprises List-of-objects, source and destination schema are set to VIEW's owner,...)
One more time I would like to complain, that definition of VIEW deserves to have the dedicated editing (tabbed) form, because views are objects not much simpler than tables. Why are they to vegetate in plain SQL Windows?
Namely, I want (many times a day) to be able to instantly compare a particular VIEW's definition across databases. Of course, there are many other types of objects, comparison of which is not trivial with PLSQL Developer (grants, roles, db links etc), but Views... views are special, we are changing them constantly.
"Normal" way would be to utilize 'Compare User Objects' but it requires the tedious setup.
The context menu's command 'Compare to Other database source' is not available for VIEWs, only for PL/SQL modules.
If only I could right-click on view name, choose 'Compare to Other database source' and... something good would happen.
For example, process could be similar to the one for PLSQL program modules:
1. prompt pops up to establish connection to 'other side'
2. immediately after successful connection ExamDiff launches with ready comparison results.
Another implementation is probably feasible only after a good tuning of 'CompareUserObjects' module:
1. I am right-clicking on a VIEW (or any other object type) name,
2. choose 'Compare...'
3. I am presented with CompareUserObjects window, prepared to comparison (i.e., only one selected object comprises List-of-objects, source and destination schema are set to VIEW's owner,...)
One more time I would like to complain, that definition of VIEW deserves to have the dedicated editing (tabbed) form, because views are objects not much simpler than tables. Why are they to vegetate in plain SQL Windows?
