Code Contents bug?

[Marcel Hoefs]

Hello,

Just recently we are experiencing a bug in the procedure editor, more specifically the code contents window. After some research we found that it is probably a parsing bug related to case expressions.

The following piece of code leads to an empty code contents window:

FOR r_var IN c_var
(b_var => CASE t_var
            WHEN 'value1'
            THEN 'value2'
            ELSE 'value3'
          END
)
LOOP
...

We are using PL/SQL developer 6.06.947 but it also occurs in trial version 7.1.0.1337

Does anybody else know of this problem and in which version of PL/SQL developer this will be fixed?

Thanks, Marcel.

 

[Marco Kalter]

We'll fix it.

 

[Marcel Hoefs]

Originally posted by Marco Kalter:
We'll fix it.

Marco,

Today I tried PL/SQL Developer version 7.1.3.1380 and in this version I still experience the same problem. As we have a lot of code where this problem occurs the usability of PL/SQL Developer is significantly compromised. In a couple of months we have to decide if we are going to upgrade our PL/SQL Developer license. A key factor for this decision is the usability of the various IDEs with our code base, so we are very anxious for a solution.

Can you tell me in which version this problem will be fixed?

 

[Claus Pedersen]

I get this error too.

It is the combination of a cursor for loop and a case statement used as parameter that causes the error.

 

[Arne Suverein]

We used to get this error too. It also occurs in TOAD.
A good alternative is SQL-Developer (free) from Oracle. Seems more robust for the more complex code.

 

[mike]

SQL-Developer. That's gotta sting, eh? I hadn't realized SQL-Developer had a code contents window yet.

That's OK - You'll get them next week!

Have a good weekend,

Mike

 

[Arne Suverein]

It also occurs in TOAD.

TOAD 9 now supports these offending CASE expressions.
When is this fixed in plsql-developer? I prefer plsqldeveloper to TOAD, but when this problem remains I cannot maintain my most important packages.

 

[Marco Kalter]

I will see what we can do to get this in a patch release shortly.

 

[Marcel Hoefs]

Originally posted by Marco Kalter:
I will see what we can do to get this in a patch release shortly.

Is the new version 7.1.4.1389 the one in which this is fixed?

 

[Marco Kalter]

No, not yet.