Recent content by Lampy

  1. L

    Bug in Beautifier

    My version is 16.0.3.2156 Immediately after pasting, beautifier does nothing Add a single new line above FUNCTION and DON'T select (highlight) anything and it fails. If I select everything, it works.
  2. L

    Bug in Beautifier

    In 16.0.3 this bug still breaks development, my 2000 line package suddenly becomes 'dead'. This simple piece of code causes ' PL/SQL Beautifier could not parse text': CREATE OR REPLACE PACKAGE BODY DPS.TTTTT AS FUNCTION xxxx RETURN NUMBER IS BEGIN FOR lcur IN (SELECT 1...
  3. L

    v12 slugish

    Is there something wrong with my computer or is v12 64bit a real slug? I mean the IDE itself ... I can see how different controls get painted, this is even worse than java GUI! If v12 is to stay this slow, I am moving away. Not to mention 50 mb exe file... definition of modern bloat.
  4. L

    Unable to try v12 64bit

    Yes, it works. Thanx!
  5. L

    Bug: pde does not import all rows

    No soup for me ... Exported with x64 v12: 15373883 Record(s) exported Imported with x64 v12: 3723026 Records loaded, 0 errors pde filesize: 622.432.256 bytes
  6. L

    Bug: pde does not import all rows

    I've tried the import with v12 ... same problem: ==================================== Import started on 6. 4. 2018 12:53:24 -- Disable triggers alter table MyOwner.MyTable disable all triggers Table altered -- Delete table delete from MyOwner.MyTable 0 rowss deleted commit Commit complete...
  7. L

    Unable to try v12 64bit

    Done.
  8. L

    Bug: pde does not import all rows

    Its big ... 622.595.703 bytes I cannot send it to you as it contains sensitive personal data. ========================================== Describe table: ========================================== stevilka, number(11), , , leto_i, number(4), y, , mesec_i, number(2), y, , stevilka_i, number(5)...
  9. L

    Unable to try v12 64bit

    We have licenced v11 and want to see if v12 works better (see the export/import bug). After starting v12 it demands a license we do not have. Must I uninstall v11 to run v12(x64) in trial mode?
  10. L

    Bug: pde does not import all rows

    ===================================== Export log: ===================================== Export started on 5. 4. 2018 09:29:31 Exporting table MyOwner.MyTable... 15373883 records exported 1 Table(s) exported 15373883 Record(s) exported Export finished on 5. 4. 2018 09:42:10...
  11. L

    Define connections - a sane Export & Import

    Export / Import connections in current form is next to useless (and buggy). Please make it so that Fixed users can be defined in a humanly readable text file in a text editor. Using XML is 21st century way of doing such things. Using Number=x and Parent=y completely destroys any chances of...
  12. L

    Enhancement request: SDO_GEOMETRY visualization

    I find that PLSQL developer almost completely ignores whole spatial stuff that oracle supports. We are thus forced to use other tools which we find seriously lacking in usability, stability and performance. It would be really great if PLSQLDeveloper had at least some SDO_GEOMETRY visualization...
  13. L

    PLSQLDeveloper SQL execution slowdown whit many predefined connections

    I have uploaded debug log to my Dropbox. Dean
  14. L

    PLSQLDeveloper SQL execution slowdown whit many predefined connections

    We found out that total SQL execution time deteriorates with many defined connection. A particular SQL was executed in 0,15 seconds when there were no fixed connections defined, just 12 different recent connections. After I imported 195 connections, the execution time of the same SQL dropped...
  15. L

    HELP: Loading BLOBs using PLSQLDeveloper

    I got this task of importing a few hundreds of images into existing rows containg empty blob column. Each row contains field FILENAME so I can determine which image to load into each BLOB field. Usual way of doing such things involves loading images onto server and then using oracle DIRECTORY...
Back
Top