Hi Marco,

where can bugs be posted? here?

i do so

Search Function in Recall Statement is not available

The disclaimer for the alpha version says that we should wait to report errors until the beta version is released, but I encountered a 'feature', that can easily be fixed, so here goes anyway:

We have enabled PL/SQL compiler warnings for our database instance.
When compiling objects, I got errors in the compilation of package bodies caused by the error "PLS-05005: function XYZ returns without value at line NNN".

This error can be removed by going into the Preferences screen, Compiler section and under PL/SQL Warning remove the action called Error (shipped with value Severe). This will make the packages compile again.

BTW, thanks to PL/SQL Developer to make these settings configurable ...

BTW II: Marco, will you make a dedicated beta tester forum like when version 7.1 was released?

[quote=Claus Pedersen]I got errors in the compilation of package bodies caused by the error "PLS-05005: function XYZ returns without value at line NNN".[/quote]
Is the error incorrect? It seems that this error would be caused when a FUNCTION has a RETURN statement without a value.

[quote=Claus Pedersen]BTW II: Marco, will you make a dedicated beta tester forum like when version 7.1 was released? [/quote]
Yes there will be. From the features list:
[quote]The Beta version will have a special forum like always to report issues.[/quote]

[quote=Worker]Is the error incorrect? It seems that this error would be caused when a FUNCTION has a RETURN statement without a value.[/quote]
Yes, it can be incorrect. It occurs for example when there's no RETURN statement in the EXCEPTION block.

After working with the alpha over the past few days, I must say I feel.... underwhelmed. I was expecting a major change [like we got from v6 to v7] with extensively new features. This feels more like just a little spit and polish.

I am an everyday user, and I must admit that I don't use most of the advanced features of plsqldev. I have noticed the code assistant "feels" faster, but I haven't noticed any other major changes.

plsqldev still quasi-randomly steals my focus and leaves child windows on top of other applications when it's busy. I have a horribly unfunctional firewall which terminates sessions after 15 minutes of inactivity, and plsqldev does not cope well with that. I get to watch the app relog in several times a day [which is quite painful on my slow connection].

However, it's still better [even if only slightly] than raptor. I can't say how long that will last given the rate at which raptor is improving.

I share the impression - the change from v6 to v7 was a remarkable greater one

/Karl

Well, to me it seems ok. It seems it's more productive, thanks to window pinning, object browser enhancements, etc.
I like the countdown seconds when executing a query, it feels faster somehow...

There are couple things to improve productivity:
a) I don't like forward declarations of procedures/functions to be on the procedure tree in package editor window, please make that configurable (I remember was it 5th or 6th version where it was ok, no forward declarations).
b) partition support is not good, no dedicated info about partition/subpartition
c) it really would be good to scroll down to line after pressing first letter of column in describe windows (now if you have 100 cols and press "z" it doesn't go to column starting with "z", however it selects it)
d) can You make dragging a column from result set to window in SQL Window will paste it's name there

Just my opinion, but somehow this is more release +1 than version +1

We have released a 2nd alpha with several fixes an an up-to-date User's Guide in PDF format.

Thank You Marco!
/Karl

When i click Objects->jobs show:
Properties of SYS.AUTO_SPACE_ADVISOR_JOB not available
Properties of SYS.FGR$AUTOPURGE_JOB not available
Properties of SYS.GATHER_STATS_JOB not available
Properties of SYS.PURGE_LOG not available

And my jobs not show. Why?