Recent content by jareeq

  1. J

    Advanced compression not uderstood by PL/SQL Developer export

    Hi, Sptet that when put table with: "row store compress advanced" when going to SQL tab receiving "compress" instead. Will be pl/sql Developer ready for advanced compression ?
  2. J

    When PL/SQL Developer will support double quoted objects

    Beta 13 is up however there is no significant difference about above. Is it implemented ?
  3. J

    Open file dialog still looks like from previous age

    Few years ago with beta testing send this message about dialog window looking so old. HERE Now back with developer 12.0.7.1837 and it still looks same. Can I reset registry keys responsible for settings of windows? Still using windows 7 without aero but guys sitting next to me use it also but...
  4. J

    When PL/SQL Developer will support double quoted objects

    Marco, what about this ?
  5. J

    Jobs tree ridiculous slow open in 12c.

    Sorry for for delay, Indeed it looks like problem in 12c however after DBA created stats it is still slow. Problem is less severe after disabling dynamic sampling in entire database.
  6. J

    Jobs tree ridiculous slow open in 12c.

    Hi, Currently using developer 10.0.5 as well as demo of 12.1 with database 12c Problem is with slow opening of scheduler jobs from objects tree. We have over 500 jobs defined, problems started from about 250. After debugging is on it looks like PL/SQL Developer spends 10-15 seconds (after a...
  7. J

    When PL/SQL Developer will support double quoted objects

    Still waiting for functionality to use double quoted objects (with special characters in name) from PL/SQL Developer interface. We have multiple schedulers defined in human readable notation for example: "USER"."Y:1:1300" But can't use this with DBMS Scheduler functionality even in PL/SQL DEV...
  8. J

    Double quoted obiects invalid in PL/SQL Developer

    thanks Marco - good to hear :-)
  9. J

    Double quoted obiects invalid in PL/SQL Developer

    Hi, I would like ask you to support in future releases of PL/SQL Developer objects that are created as double quoted using special characters. For example, currently if you create scheduler named "A:b:c:D" you can't call it with job since it tels there is special character or object not exists...
  10. J

    Purge Recycle bin button with shift

    This is some like enhancement request. While drooping table that would be nice to have feature to purge it directly when Shift+Drop is pressed simultaneously rather than move to recycle bin. (like windows recycle bin :-)) Cheers, Jarek
  11. J

    ORA-1722 Invalid Number - Import PDE

    Yes - I used this method to check what settings do not cause errors in the import of PDE files. But it would be better and more comfortable if the patch would be available :-) Anyway Thanks.
  12. J

    ORA-1722 Invalid Number - Import PDE

    Marco, My license does not cover the current version 9.0 (as I wrote before - I have only demo 9.0). I'm corporation rat :-) ... it will take some time before I can benefit from this fix. So can you make exception and do the fix to the highest version of PL\SQL Developer 8.0 too ?
  13. J

    ORA-1722 Invalid Number - Import PDE

    Ok this is my NLS parameters From database and User. Like said before NLS_NUMERIC_CHARACTERS differ as well as other. But in the versions below 802 it does not matter - over it yes. User - NLS Session Parameters Parameter Value NLS_CALENDAR GREGORIAN NLS_COMP BINARY NLS_CURRENCY zł...
  14. J

    ORA-1722 Invalid Number - Import PDE

    Back again with this issue on v9. Symptoms like above. Re installation or fresh installation do not resolve issue (only downgrade to v802). Like previous - data export file (pde) in versions over v802 of PL\SQL Developer contains dot '.' as separator in number values. In v802 and lower -...
  15. J

    ORA-1722 Invalid Number - Import PDE

    Marko, Solution for this issue is not installing 8.0.4 over 8.0.0 (with first installed 8.0.0 everything works fine). So clean install of 8.0.4 do the trick and solve ORA-1722 Invalid Number in my case.
Back
Top