Test window pl/sql dev 6.0.1848

[IanBradshaw]

I've just downloaded the latest version of pl/sql developer and theres features that used to be in the test window that are not currently there. If I highlight a select statement and then choose test, it used to take it into the test window and list any variables in the window below. If the select statement was selecting values 'into' variables this section would be commented out. This doesn't seem to work any more with this version. Has this been change or am I imagining things?

 

[Marco Kalter]

Works fine for me. Can you let me know the exact steps to reproduce the issue?

 

[IanBradshaw]

I just did it the same was as I did with the previous versions. I have a script in the command window, I highlighted a select statement, right clicked on it and chose 'test' from the menu. A query I tried was:

select jcategory category, section, print_order
from bs_budmon_categories
where jclcode = v_client
union
(
select jcategory category, 3, 99
from repair_type
where client = v_client
minus
select jcategory, 3, 99
from bs_budmon_categories
where jclcode = v_client
)
order by 2,3,1

Previously the variables would be automatically picked up in the window below. Also if i have a query such as:

select j_doc_compl ,
jraised ,
week_comp ,
year_comp ,
jstatus ,
jjondate
into v_date_comp,
v_raised,
v_week_comp,
v_year_comp,
v_status,
v_on_date
from jjobh
where jjobno = p_job_no;

The into part would be automatically commented out. It's not that big a deal I was just wondering why it worked before and not now, it was also a bit of a time saver.

thanks,
Ian

 

[Marco Kalter]

Both statements work fine for me. I had to replace the tables and columns with emp table equivalents though, because I do not have your table definitions.

I can only imagine that you are connected with a user that does not have select privileges on the jjobh, bs_budmon_categories and repair_type tables. Could this be the case?

 

[cmj]

This sounds like an interesting feature I have missed, but I don't see how it works and I can't find it in the documentation. Can you point me to documentation or give a more specific description of how to use it?

 

[IanBradshaw]

I have privileges on all these tables, the feature worked the day before I updated but now unfortunately it doesn't. It seemed to be able to pick up the variables in the query and set them up for me in the window below. I could then select the field type and put in sample data to test. It now just comes up with the query in the test window but nothing in the box below. I have to manually change the variables so that they have ':' in front of them and then rescan the variable window below.

 

[Marco Kalter]

@IanBradshaw:
That's strange. Can you let me know your Oracle Server version?

@cmj:
If you select a select statement in a PL/SQL editor and right-click on it, you will see a "Test" and "Explain Plan" menu item. In 6.0, these functions create a Plan Window or Test Window where the PL/SQL variables in the SQL text are replaced by bind variables, and where the "into" clause is removed (so that you get a result set). As a result you can get the query plan without modifying the SQL text, or test the statement by supplying appropriate values for the variables.

 

[IanBradshaw]

Hi Marco, I'm using Oracle7 Server Release 7.3.4.5.0.

It's just weird how it worked in one release but not in the next.

 

[cmj]

Thanks for the explanation. That's another good reason for me to upgrade to 6.0.

 

[Marco Kalter]

@IanBradshaw:
Ouch. We'll try to reproduce this. We made a change from 6.0.0 to 6.0.1 to fix a problem on 9.0 and earlier when using record type variables. My guess is that this broke Oracle7 compatibilty for this function.

 

[IanBradshaw]

Sounds like it might be the root of the problem Marco, is it possible to fix it?

 

[Marco Kalter]

It was okay for 6.0.0, we broke it for 6.0.1, so I assume we can fix it for 6.0.2.

 

[IanBradshaw]

Great Marco, thanks again.