When I "Edit" a table in a SQL window and use the binocular to query data (e.g. the second field) then the resulting query does not have the entered data but :var2. (e.g. select t.*, t.rowid from lrm_communicatiemiddelen t
where cml_waarde = :var2) This seems to be the case only for varchar2 column.
No, this is not XML related. If I do: New test window, create a temporary Clob variable and click on [...] to edit it's content then it will take same amount of time. So this is an empty Clob.
Yes, it's a XML text.
I did some additional testing. Logged in from another client to the XP Oracle database and got about the same performance as under Linux, fast, so it must be something local. Switched off all firewall and anti virus software but still slow performance when on the local...
Is there also a new new session being created when I open the Large Data Editor? I don't have any problems with the normal SQL Windows but as soon as I open the LDE then it may take up to 45 secs before the CLOB's data pops up. I noticed the same behaviour as Makker did. It's lightning fast...
I always use the following piece of code to prevent the debugger from hanging:
i binary_integer;
i := dbms_debug.set_timeout(timeout => 60);
put it at the start of the procedure/function to debug.
I like to have some hierarchy in the reports directory and created sub-folders in this directory. PL/SQL dev does not recognize the subdirectory until I place a dummy report in the parent directory. But I don't like to see this dummy. Is this expected behavior or am I just using a "feature"? Is...
I found that the order of the columns is important when comparing two database objects.
DB1:
create table PIL_UNITS_OF_MEASURE
(
ID NUMBER(12) not null,
CODE VARCHAR2(10) not null,
ACTIVE VARCHAR2(1) not null,
DESCRIPTION VARCHAR2(1000),
SCALE...