PLSD 8 within 2nd quarter - Countdown - Allround Automations forums

12 days to go!

11

10.5 ;-)
/Karl

They are going to make us suffer untill the last day

does it help if i am in new zealand? i am a day ahead of most of the world...

8 days left

Here's the sql for it:

Code

select today, end_quarter2, ( end_quarter2 - today ) as days_to_go from
  (select trunc(sysdate) today, to_date('30.06.2009','DD.MM.YYYY') end_quarter2
     from dual);

Still 8!!!

Code

SQL> 
SELECT Today
      ,End_Quarter2
      ,(End_Quarter2 - Today) AS Days_To_Go
  FROM (SELECT Trunc(SYSDATE) Today
              ,To_Date('30.06.2009'
                      ,'DD.MM.YYYY') End_Quarter2
          FROM Dual);
 
TODAY       END_QUARTER2 DAYS_TO_GO
----------- ------------ ----------
22.06.2009  30.06.2009            8
 
SQL>

/Karl

7 !!!
:-)

Code

June 19, 2009
Direct Oracle Access 4.1.2 for Delphi 2009 and C++Builder 2009 released

If the release schedule of the 2 products is closely related then it shouldn't be much longer ...

6!!! Less than one week to go!

5 !!!

4 !!!

1 to go...

Common guys, I can't sleep at night

.

still 1 to go
/Karl

Now. We can access ...
http://www.allroundautomations.com/plsqldev80.html

But, there isn't any topic.

0!

Countdown completed!
/Karl

0 days to go. You can download a preview version here. Note that this is a preview version only, and that a formal beta version will be available in July.

Given that you don't want any feedback on this, I'm assuming this is 100% just to make us happy. So thank you! (It worked. I'm happy

)

And with a New Features list! Perfect! I'm happy too!!!

Thank you very much!!!
/Karl

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?

Does anyone expierence stability problems with Alpha2? I ran PLSQLDev A2 once and it worked, I closed it and I can't get it to run second time

Debug.txt doesn't contain any clue what's wrong (for me at lest)... Alpha1 (reinstalled over A2) works fine...
Consider this as a question only as I'm running it under Wine in Linux, so my debug output probabaly will not be considered as useful

Alpha2 does not seem to work with Instant Client.
I have no Oracle Home. Been using Instant Client for a while.

[Linked Image]

it works with instant client for me...

Pl/Sql Alpha 8:

Just installed it a few hours ago...

Ok looks the same as 7, but I really like new enhancements:
- Browser auto hide
- Browser objects find
- Files browser
- Wait time in sql window with sound for long queries.
- Beautifier enhancements

Can't wait to use production version....

OK, never mind. PLD requires the full path of the OCI DLL. I only specified the directory earlier.

When will the beta version be released?

And when will the beta tester forum be opened?

The issues seems to pile up in this post, and that can not be intentional.

I have one issue, though. I have switched on the option "Show variable and type declarations in a popup". This works great, thanks, but there is a tiny inconvenience: when the popup is shown at a line near the bottom of the screen (for instance showing a cursor declaration that extends over several lines), the bottom lines are truncated.

up

I know we've been asked to refrain from comments/bugreports etc. until the release of Beta8 and the subsequent opening of the 'beta forum', but I still would like to comment on one of the new features of the editor, i.e. autoindent. The following piece of code was written using autoindent:

Code

PROCEDURE demo
  IS
  <declarations>
  BEGIN
    IF
      THEN
        <CODE>
        FOR <iterator>
          LOOP
            <CODE>
            END LOOP;
            END IF;
            END;

I don't think it is logical for 'IF/THEN' 'FOR/LOOP' constructs to autoindent on both keywords. These 'coupled keywords' (for want of a better description) should be treated as one keyword (leaving aside that in my opinion 'IS' should not be considered for autoindentation).

Furthermore I'd like to suggest that autoindent is combined with auto-unindent so that

Code

   IF
   THEN
     <code>
     END IF;<cursor position>

after hitting 'enter', would change into

Code

   IF
   THEN
     <code>
   END IF;
   <cursor position>

Then the first sample code block, using the same keystrokes would look like this

Code

PROCEDURE demo
IS
<declarations>
BEGIN
  IF
  THEN
    <CODE>
    FOR <iterator>
    LOOP
      <CODE>
    END LOOP;
  END IF;
END;

Just my two cents (and looking forward to beta8)

[quote]I don't think it is logical for 'IF/THEN' 'FOR/LOOP' constructs to autoindent on both keywords. These 'coupled keywords' (for want of a better description) should be treated as one keyword (leaving aside that in my opinion 'IS' should not be considered for autoindentation).[/quote]
Note that you can edit the SmartIndent.txt file to match your coding style.

[quote]Furthermore I'd like to suggest that autoindent is combined with auto-unindent so that[/quote]
I have added this to the list of enhancement requests.

[quote]
Note that you can edit the SmartIndent.txt file to match your coding style.
[/quote]

Indeed, that fixes (part of) the problem.