Well, it is about editioning views and maybe even not specific to version 14. It works indeed with "real" tables.
Making it work for editioning views (or even better all views) would be great. I think this is failing in such cases because it is trying to get the foreign key relations from the view.
When connecting via VPN to a remote database the performance is not sufficient. This applies especially to compare operations (timeouts, "user requested the cancel of the current operation"(without requesting a cancel)) etc.
Seems that the a 4K display could be part of the problem, operation...
Compare user objects wrongly detects diffenreces when "char" semantics is used. When the diffreneces are applied byte semantics is "enforced".
This is for all UTF DB charactersets a real issue.
PLSD version:
13.0.6.1911 (64 bit)
Oracle DB 12.1 ... 19c
The simplest example:
on the source:
CREATE TABLE tab1 (testcol VARCHAR2(10 CHAR));
SELECT table_name,data_type,char_length,char_used FROM user_tab_columns WHERE table_name='TAB1';
TABLE_NAME DATA_TYPE CHAR_LENGTH CHAR_USED
1 TAB1 VARCHAR2 10 C
compare to target (the...
When comparing (and applying after compare...) tables the varchar2 are always compared with byte semantics. This seems to be wrong.
Version: 13.0.6.1911
Dezs
Linked query button is not doing anything.
Version 11.0.4.1788 (64 bit) (same for the 32 bit version)
Seems this is happening when selecting from some synonym which again is pointing to some view in a different schema.
In such a situation the "Custom..." entry is not shown preventing the...
I have also seen this happening a couple of times with the x64 version (and no I can not reproduce this on will). This can be seen as something dangerous (e.g. autoselect "decides" to do some update statement instead of the intended select)