UNIDAC show clob has erors in direct mode for oracle
UNIDAC show clob has erors in direct mode for oracle
now i use the new version of unidac;
this bug were found half a year ago.
i waiting the new version and hope it can solve it.
but new version can't too.
for example;
the sql is:
BEGIN
v_clob := 'ss';
v_clob := v_clob || v_clob;
v_clob := v_clob || v_clob;
v_clob := v_clob || v_clob;
v_clob := v_clob || v_clob;
v_clob := v_clob || v_clob;
v_clob := v_clob || v_clob;
:SCRIPT := v_clob;
END;
the delph code is:
begin
uniQuery1.sql.text:=memo1.text;
uniQuery1.parambyname('SCRIPT').DateType :=ftOraClob;
uniQuery1.execute;
memo2.text:=uniQuery1.parambyname('SCRIPT').value;
end;
in oci mode:
memo2.text:='sss....ss';
in direct mode:
memo2.text:='sss....ss? ';
but this bug is sometimes show ,not every time show;
so we must test and test.
this bug were found half a year ago.
i waiting the new version and hope it can solve it.
but new version can't too.
for example;
the sql is:
BEGIN
v_clob := 'ss';
v_clob := v_clob || v_clob;
v_clob := v_clob || v_clob;
v_clob := v_clob || v_clob;
v_clob := v_clob || v_clob;
v_clob := v_clob || v_clob;
v_clob := v_clob || v_clob;
:SCRIPT := v_clob;
END;
the delph code is:
begin
uniQuery1.sql.text:=memo1.text;
uniQuery1.parambyname('SCRIPT').DateType :=ftOraClob;
uniQuery1.execute;
memo2.text:=uniQuery1.parambyname('SCRIPT').value;
end;
in oci mode:
memo2.text:='sss....ss';
in direct mode:
memo2.text:='sss....ss? ';
but this bug is sometimes show ,not every time show;
so we must test and test.
-
- Posts: 1
- Joined: Mon 12 Mar 2012 21:19
+1... I tried to work through this a few months ago, and could not figure it out with the bug. I put it off until you guys figured it out, and I just realized that it has been fixed! thanks for getting this error cleared.

Las Vegas hotel deals | List of Las Vegas hotelsdaizhicun wrote:thanks , the new vision has fixed this bug
Re: UNIDAC show clob has erors in direct mode for oracle
Hi, i do have this issue within the 4.1 version (not the latest one as i didn't renewed my license yet), however it should be fixed in this release isn't it ?
Using unicad 4.1 in delphi, with an Oracle 11 database, using the OCI mode everything is fine, using the DIRECT mode i can't update CLOB fields without receiving a ORA-01460 error. Any clue?
Using unicad 4.1 in delphi, with an Oracle 11 database, using the OCI mode everything is fine, using the DIRECT mode i can't update CLOB fields without receiving a ORA-01460 error. Any clue?
Re: UNIDAC show clob has erors in direct mode for oracle
You are using an obsolete UniDAC version, please try to reproduce the problem on the latest trial UniDAC version 6.0.2 http://www.devart.com/unidac/download.html , and if the problem repeats, contact us again.