Recent content by protos

Ok! Nice to hear.

No, our database is CL8MSWIN1251. We use export in UTF for source control.

Hi. Why tool "export user objects" does not use encoding options and always export in ANSI (in my case). Is it a bug? pl/sql developer v12

Hi. What about whis problem? Main problem - When current schema changed in initializations SQL Sсript (connection manager), than PLSQL developer not display compilation errors. It's makes use extremely uneasy.

We have limited connections per user.

Yes, but after changing current schema PLSQL developer not understand this and some functionality does not working. Such as describe table, or code assistant, or ctrl-click on table or package. I believe that is because PLSQL Dev thinks that he is in original schema.

it's working only for one schema. If I want to change current schema after connection, I forced out to reconnect to connection with different initialization script. It is not handy.

Hi. In our organization all developers login in database with his own usernames/passwords. Then change current schema and working with objects in that schema. In toad there are useful functionality - combobox for change current schema. PLSQL Developer not perfectly working in this case, even...

Output truncating not reproduce, when I change nls_lang from "AMERICAN_AMERICA.CL8MSWIN1251" to "AMERICAN_AMERICA.AL32UTF8" on my PC. But it is not a solution, unfortunately.

I have 9.0.6. But output truncated. And my DB use UNICODE, if it is important in this case.

Hi. Is this PL/SQL developer restriction for output string with length more than 4000 characters? In next example I see only first 4001 characters in output: BEGIN dbms_output.put_line(LPAD(' ',4000,'1')||LPAD(' ',4000,'2')); END;