Recent content by Kuba

  1. K

    Bug in comparing

    We have this problem still: target: differences:
  2. K

    Bug in comparing

    I found bug in PL/SQL Dev 6.0.4 in comparing: source: -- Create table create table RODZAJ_OBIEKTU ( ID_RODZAJU_OBIEKTU NUMBER(9) not null, KOD_RODZAJU_OBIEKTU VARCHAR2(15) not null, NAZWA_RODZAJU_OBIEKTU VARCHAR2(30) not null, DOSTEPNY CHAR(1) default 'F' not null...
  3. K

    Next bug in comparison

    There is another bug in compare processor. Try to create in DB1 such table: create table TEST ( A VARCHAR2(10) not null, B INTEGER not null ) tablespace USERS pctfree 10 initrans 1 maxtrans 255 storage ( initial 64K minextents 1 maxextents unlimited ); --...
  4. K

    Two bugs

    I understand, you're right, but, as I wrote, I'm using constants in select statementens in PL/SQL stored procedure. Very often I need to check explain plan of such query. Then I mark it in stored procedure editor and press 'F5' to explain plan. If in query is any parameter reference plsqldev...
  5. K

    Creating functional indexes

    Great! Thanx!
  6. K

    Two bugs

    1. Thanx! 2. That's not true! I'm referencing constants in select stataments very often - in stored procedures, and it works!
  7. K

    Creating functional indexes

    Could you implement in PL/SQL Developer a designer to creating functional indexes? Now, in table editor, on 'Indexes' bookmark I could in very simple way create normal index using 'Select index columns' dialog. But if I want to create functional index (what I need do very often in polish...
  8. K

    Two bugs

    There are two another bugs in PL/SQL Developer: 1. Not null, deferrable, initially deferred constraint problem. Try to this command on any table: alter table table1 add f1 number(8) not null deferrable initially deferred; In 'Oracle Enterprise manager console' in table editor this column...
  9. K

    Compare user objects next bug

    I found next bug in comparing in 6.0.1. In source db: create table ESPRAWY ( ID_ESPRAWY NUMBER(8) not null, TERMIN_ESPRAWY DATE, DATA_WSTAWIENIA DATE default sysdate not null, DATA_ZAKONCZENIA DATE, OPIS_ESPRAWY VARCHAR2(768)...
  10. K

    Bug in XML editor

    Are you working on this?
  11. K

    Bug in XML editor

    There is a bug in XML editor too. 1. I'm opening CLOB field and the XML viewer is showing 2. The first line of XML document is <?xml version="1.0" encoding="iso-8859-2"?> 3. I'm putting one space somewhere and pressing "OK" 4. then opening CLOB field again and the first line is now: <?xml...
  12. K

    Bug in "Compare user objects"

    I think there is a bug in "Compare user objects" tool. Steps: 1. create simple table in two databases, for example: create table TESTDIF ( FIRST VARCHAR2(20), SECOND VARCHAR2(20), THIRD VARCHAR2(20) ) 2. in one database drop column "SECOND" 3. use "Compare user objects" on table...
  13. K

    Problem with charset encoding

    Ok, I know now where was the problem. There was enviroment variable 'NLS_LANG' setted on 'polish_poland.ee8iso8859p2'. I removed it and everything is fine. But this is not a good solution. I need this variable for other purposes. I think that in PL/SQL Developer should be option to ignore this...
  14. K

    Problem with charset encoding

    Hello! I have problem with charset encoding in plsqldev 6.0. In database charset is set on ISO-8859-2. When I browse table data in Oracle Enterprise Managment Console everything is fine (there is no any strange marks). In plsqldev I get text data in other encoding - it looks like Windows-1250...
  15. K

    New feature request

    We archive all Oracle stored procedures in .prc files - we can use CVS then to management. When we want to edit procedure we always open procedure content with its .prc file. There is a problem where somebody compile procedure and doesn't save it. Could you make option, which could cause save...
Back
Top