well, if the user really has SELECT ANY DICTIONARY as written above, then yes, he has select priviliges on dba_views
i
for me a similar issue has not worked for several releases now. as a workaround, I use the commandline switch "oldnameresolve", maybe this also...
the link above shows the option to use InlineObjectMenu command line parameter to enable to work more efficiently
can this be officially documented in the user guide? (as I cannot find it)
I just installed plsql developer 15 to test.
I almost exclusively in full screen mode to see more lines of code, in addition to have more lines visible I have deselected sdi in view menu. However now, whenever I switch to full screen mode, it seems it switches to SDI despite having it...
hi,
when I use hide editor to display only the result grid, and then revert again, I can no longer resize the result grid up/down in plsql developer 14.
Stefan
you cannot, according to: https://docs.oracle.com/database/121/SQLRF/statements_8004.htm#SQLRF01504
there it says:
If the subquery uses an asterisk (*) to select all columns of a table, and you later add new columns to the table, then the view will not contain those columns until you re-create...
what is the status of this request?
can you at least check only once per user and database?
at the moment when there are 6 windows open with the same connection, pl/sql developer tries 6 times, so I have to wait 6 times for the timeout for not available databases
it seems, they do not care, another post regarding the same problemhttps://forums.allroundautomations.com/ubb/ubbthreads.php?ubb=showflat&Main=12429&Number=47105#Post47105
Yes, that is what I thought they were and with above bind variables, they evaluate to true.
IF a table has 30'0000 subpartitions then this query generates 30'0000 identical rows. This will be a performance problem, unless of course, internally only the first row is considered.
When describing a table (right click, describe), the following statement is executed:
select t.*, o.*, m.comments
from sys.dba_tables t,
sys.dba_tab_comments m,
sys.dba_objects o
where t.owner = :object_owner
and t.table_name = :object_name...
Yes, noted.
As far as I know, most performance related issues where related to changes in all_-views, as long as I use dba_-views I should be fine (at least I did not encounter any issues up to 11.2 yet, unlike others on this forum)
I think a found a solution here in the forum, the parameter OldNameResolve
As this is not documented in the manual:
Are there any restrictions or plans to remove this parameter?
Stefan
I have a question regarding the options when I right click on a package or table:
when I have granted select catlog role and selected use dba_view, I can view the all objects definitions from the object browser.
When I right click on an object I can only view objects I have the privileges to...