Recent content by AdamG

  1. A

    Function Compare to saves always as ANSI

    Looks like there was diffrent procedure when file is saved from editor using "Save as" function and when saved for any compare function ( here is some kind of worng and not needed conversion from already UTF8 in edit window to ANSI ). My ukrainian letters are converted to question marks, same...
  2. A

    Function Compare to saves always as ANSI

    I have my package body saved to file and when just after save I use Compare to -> Current file... I have Window.pcf saved as ANSI not UTF-8. See on screenshot
  3. A

    Function Compare to saves always as ANSI

    My preferences attached
  4. A

    Function Compare to saves always as ANSI

    Aditionally I have NLS_LANG=polish_poland.ee8mswin1250 for my ansi codepage to oracle and in %APPDATA%\PLSQL Developer 15\params.ini i have nls_lang=polish_poland.utf8 to compile in utf8
  5. A

    Function Compare to saves always as ANSI

    PL/SQL Developer Version 15.0.3.2059 (64 bit) 263.142721 - 10 user license Service Contract: 2023-06-01 Style: Office Dark Windows 11 Build 22621 pl-PL(1045)/Polski (Polska)
  6. A

    Function Compare to saves always as ANSI

    That's enabled. I don't have any problems with opening files which are UTF8, typing and compiling the code. All works, and UTF8 characters are not lost. It happens only when files are saved for external comparation.
  7. A

    Function Compare to saves always as ANSI

    Hi, my database is AL32UTF8, I have in preferences/Files/Format/Encoding -> Always UTF8, but when I use function to compare my edit window to current database source both files ( Editor.pcf and Database.pcf ) are saved with ANSI encoding so I have all characters which are not in my ANSI codepage...
  8. A

    Export User Object ignores encoding settings

    Can we have that fix in current 15 beta ?
  9. A

    Export User Object ignores encoding settings

    Hello! I have selected in my Preferences/Files/Encoding option Always UTF8. It works when I save object from edit window. But when I do export using Tools/Export User Objects it does create all files in ANSI. It confuses my git repo. Adam
  10. A

    "Compare User Objects" enhancement request

    Hello Marco, any chance to get this any time soon? Thanks, Adam
  11. A

    PL/SQL Developer 10 - "Compare User Objects..." - triggers

    I've noticed that schema prefix issue has something in common how oracle stores trigger definition. For some unknown reason, when I do select description from user_triggers I get some triggers in normal format like t_my_trigger before insert.... but some of them are stored with schema owner like...
  12. A

    v10 vs v9: Performance problems with "Compare User Objects" and "Export User Objects"

    Looks more like problem described in PL/SQL Developer 10 - "Compare User Objects..." - triggers. Because in my case there are triggers in destination schema which are not in source, but I don't want to loose them... And here is the case when two compared triggers are different only by schema...
  13. A

    Compare User Object new behaviour in v10

    Hello, I've noticed that when do compare two tables connected to schema owners and source table has less triggers than table in destination schema, there will be drop trigger generated. This is very dangerous for me because I have some basic set of triggers in dev schema and often some more in...
  14. A

    Debuger with Oracle11 bugged

    Hi Marco, Did you manage to reproduce it?
  15. A

    Debuger with Oracle11 bugged

    Hello, I noticed some problems with debugging when connected to Oracle11. When program unit which you debug step by step throows an exception PL/SQL Developer hangs. For test I created a procedure with sthg like dbms_output.put_line(5/0); inside and exception didn't appear. Instead Developer...
Back
Top