New answers tagged oracle-sql-developer
I think you need to either qualify type with schema when using client account (CO_ADMIN.DOCPARAMETERTYPE_TABLE, not just DOCPARAMETERTYPE_TABLE ) or create a public synonym for the type.
You could check V$TRANSACTION. Here is an example: create table t(a number); Table created. insert into t values (1); 1 row created. select t.status from v$transaction t join v$session s on t.ses_addr = s.saddr where s.sid = sys_context('USERENV', 'SID'); STATUS ---------------- ACTIVE After commiting: commit; Commit complete. select t.status from ...
Views starting with VW_DTP showing up in the execution plan is the result of one of the cost-based query transformations available since 11.2, called distinct placement. It happens with statements using the DISTINCT clause, just like yours. It is an absolutely acceptable an quite obvious execution plan to join the tables and filter the rows, and after that, ...
I agree that a temporary table (or "hash table" # in SQL Server speak) will do what you want. If you want to do this graphically I can recommend a product called "Lavastorm Analytics BRE". There is a free desktop version and it will allow you to view datasets on the fly. It can also do a few things you can't do with conventional SQL such as an inner and ...
It seems to me that you might want one of two things to do what you require. 1) could be global temporary tables (GTTs), see here or here. Check out the Oracle docco here for drier technical detail. 2) might be CTEs - Common Table Expressions (or subquery factoring as Oracle calls it) - also known as the "WITH CLAUSE". Howtos are here and here - (again, ...
The green bug you're seeing (look closely) means the package have been compiled with DEBUG option. It is also seen on bare procedures and functions. It is a coincidence they don't expand - maybe a bug (duh) in SQLdeveloper :) On mine, these expand without problem.
Top 50 recent answers are included