Enhancements & bugs

[Kirurgs]

I'm using Developer for a while now (like 3 years), it's the best development IDE i have ever seen.

I's missing just a few things I would like to see:

1. if collection is defined as record type array, it would be nice to see description for elements, example:
type t is record (a varchar2(10));
type t1 is table of t;
v t:=t();
so, description is needed for v(1). => a, v. => a... (I hope the point is clear)

2. description of a table, section "Copy comma separated" => comma before each column (not after)

3. procedure names in package body section what is in header also, I would like to see in defferent color, font etc., so I see what isn't/is included in header

4. do not show procedure/function declarations (like defined in header) in package body

5. extracting wiew/trigger/package/table sources from DB with owner included, like: create or replace package SCOTT.my_table...

6. in the debugger, when debugging collections, I can't see value for index what is expression not constant, exmaple: v_col(v-a).value -> no information is displayed for that

Bug:
in editor, sql windows sometimes right click and describre doesn't point to right table, it's showing previous table described...

 

[Marco Kalter]

I have added your suggestions to the list of enhancement requests. About the editor bug: can you let me know the exact circumstances to reproduce this?

 

[Kirurgs]

Now I'm at home, but tomorrow I'll check for sure, but as I remember it could be in case if Oracle session ends while developer is opened, then after recconect it could happen...

 

[Kirurgs]

Ok, there ar conditions:
connect to Oracle, using already opened SQL Window write down table name like DEPARTMENTS, try to describe table using right click, it won't show describe option in popup menu, then write down another table like AGENTS, when right click and describe AGENTS it's describing DEPARTMENTS not AGENTS...
Workaround: I have to write schema owner.table_name like SCOTT.AGENTS, then it describes correct table...

 

[Marco Kalter]

Works fine for me. Can you send me the complete SQL Window contents to make sure that we are doing the same thing? Are you using 6.0.4?

 

[Kirurgs]

Using 6.0.4.906 developer...

I'ts easy reproducible, i just forgot that it should be with contents in it

Open new sql window, paste the text:
SELECT * FROM SYS.dual WHERE ROWNUM=1
(NOTE: bug is reproducible only when where clause is applied), then write dual, then try to describe, it won't show describe option, then on new line write v$session then describe and woops, it's describing dual

 

[Kirurgs]

Just tried, it's simplier than I thought
So paste the text below, and try to describe dual...

SELECT * FROM SYS.dual WHERE ROWNUM=1
dual
v$session

 

[Joachim Rupik]

Such statement is incorrect. It has a syntax error. The Word "dual" in a second line means nothing just a word "dual" - it is not an oracle object, because of syntax error. So the behaviour of PL/SQL Developer (no describe) is absolutely correct !
By the way, it should also not to describe "v$session" in a line no 3 (just my thought) .

Joachim Rupik

 

[Kirurgs]

No you are wrong, DUAL is Oracle table name as V$SESSION is!!!

And "...The Word "dual" in a second line means nothing just a word "dual" - it is not an oracle object..." - you can't say it that way, then also v$session on 3rd line is just a word "v$session", there are some mistakes in your thoughts I think

In the example I added dual and v$session tables as they exist in all oracle databases and give correct description of a bug, I can't give just table names in my project as Marco won't have them in his database

P.S. Letters skdfjsdfg are just nothing, but they also can be a table name you know

 

[TenGor]

Hy,

well you don't have to execute this statement.
This really won't work.
Just type it and rigth-click on either dual or v$session.
If you add another line with "Dba_Users" and let PL/SQL describe this table, you will get the desc from v$session.

 

[Kirurgs]

And enhancement Nr. 7:
in debug mode it would be nice to see values in expressions like v(1).a or see all record values in collection, like v(1).a => 10, v(1).b => 20

Would this and above enhacements be implemented in near future?

 

[whip]

Originally posted by Kirurgs:
No you are wrong, DUAL is Oracle table name as V$SESSION is!!!

Just a guess, as the text contains syntactic errors: PLSQL Developer might recognize v$session as an alias to dual (as in select * from dual v$session)

 

[Kirurgs]

It can't be so

SELECT * FROM SYS.dual WHERE ROWNUM=1
dual
v$session

As you see, there is also WHERE clause present, so it can't be alias...

But I found an error in my statement: v$session is NOT a table, it's view
Fortunately in this context it doesn't matter