Recent content by puchtec

  1. P

    Test Window does not supprt Variables of type TIMESTAMP

    The current version 7.1.4.1389 of PL/SQL Developer does not support variables of type TIMESTAMP, TIMESTAMP WITH TIME ZONE, TIMESTAMP WITH LOCAL TIME ZONE in the Test Window. Could you please put this on the list of enhancement requests? Thanks in advance, Frank
  2. P

    Object List in Browser when working with Proxy User

    Hi Marco, thanks for the response. I am looking forward for the implementation of this enhancement request. Cheers, Frank
  3. P

    Object List in Browser when working with Proxy User

    I am connecting to my database using a proxy user (introduced with 10g). Example: CONNECT connect_user[table_owner_user] Using filter "My objects" the browser filters the correct objects (all objects of user "table_owner_user") - BUT all objects are prefixed with "table_owner_user". Instead...
  4. P

    Bug, Page Setup does not work

    Hi Marco, is the downloadable file you posted an official released and supported version (I guess it's version 7.1.4.1390)? I would avoid to roll-out build 1389 right now if there already exists a newer build. Cheers, Frank
  5. P

    7.1.4.1389: Hanging while pressing right Mouse-Button

    On my installation (7.1.4.1389 on Win XP) the first right click goes fast - the next clicks will bring the pop-up with a short delay. However, this only seems to happen in the program windows.
  6. P

    Explain Plan Window does not support XQuery

    This works fine. If afterwards I run SELECT * FROM TABLE(DBMS_XPLAN.DISPLAY()); I get a correct execution plan. You can use this code to create the sample table: CREATE TABLE xml_test(test_xml XMLTYPE); INSERT INTO xml_test VALUES...
  7. P

    Explain Plan Window does not support XQuery

    I tried to get the explain plan from a SQL statement like: SELECT XMLQuery('for $i in /test_list return {xs:integer(fn:sum($i/val))} ' PASSING test_xml RETURNING CONTENT) FROM xml_test; but I get an error...
  8. P

    plsqpldoc: wrong size for character semantics

    I generate plsqldoc for a table having columns specified in character semantics, e.g. VARCHAR2(30 CHAR). I am wondering why I am getting a documentation with the four-times size, e.g. VARCHAR2(120)? Wouldn't it be possible to generate o a documentation with VARCHAR2(30 CHAR)?
  9. P

    plsqldoc Plug-In and Conditional Compilation

    I tried the new Oracle 10g R2 feature for Conditional Compilation (I did this in Oracle 9i R2) and found that when generating the documentation using plsqldoc (1.2.0) it hides all that stuff that is below my $$ lines :confused: Does anybody hit the same problem? Any ideas?
Back
Top