lot of bugs

[tblt]

1) ODBC importer bug :: i have created and fully acceselable ODBC data source (for FireBird). after executing, in CLOB fields in destanation table (BLOB fields in source table) i see repeteabled data for each 50-100 rows. For example, BLOB field in source contains like that
'AAAAAAAAAA' (first row)
'BBBBBBBBBB' (second row)
'CCCCCCCCCCC' (third rows)
etc.
in destanation table
'AAAAAAAAAA' (first row)
'AAAAAAAAAA' (second row)
'AAAAAAAAAA' (third rows)
etc ...

2) debug bug :: when i add varitable in watches window by right click, when debugger wait for breakpoint, while my procedure is still executing, plsqldeveloper immediatly crashes (Access violation ...).

 

[tblt]

sorry, forgot:
Oracle 9.2.0.5
Plsql developer 7.0.3.1123

 

[Marco Kalter]

We'll look into the ODBC importer bug.

About the crash: please send the pslqldev.log file from the PL/SQL Developer installation directory to support@allroundautomations.com.

 

[tblt]

Originally posted by Marco Kalter:
We'll look into the ODBC importer bug.

About the crash: please send the pslqldev.log file from the PL/SQL Developer installation directory to support@allroundautomations.com.

Ok. i'll send when this eroor occur next time.
A) not a bug, but ...
1) i Open package body for edit.
2) i creating new table (rigth mouse click on "table", choice "new", fill all required items, and then press "Apply" button),
3) in opened source this object not showed in code assistant. After logoff/logon all ok. maybe just needed refresh TList in "Code assistant" on event "Apply" ?
B) Bug in debugger. If i type any text for string (varchar etc) parameter in win1251 codepage (in varitable definition area), in result of binding, my procedure take of value in UNICODE value. This not happen when i call proc like that :

begin
-- Call the function
:result := iotd_manage(
i_iotd_id => :i_iotd_id,
i_td_name => 'Win1251_Cp',
i_or_name => :i_or_name);
end;

C) Where i can see an current BUILD for plsqldev? I don't want download 15m for checking this

 

[Marco Kalter]

C) Where i can see an current BUILD for plsqldev?

All that matters is the major.minor.patch (e.g. 7.0.3) number. The build number is not significant.