We're getting the usual
"can bind a LONG value only for insert into a LONG column"
on an execute with a TOracleDataset on a UTF8 database. The code worked perfectly on 8i. The code also works perfectly if the session property UseOCI7 set to true, this isn't really an option.
We think the error is occuring as Oracle 9.2i has tightened up its binding. The field type thats causing the problem is defined in Delphi as a ftString (String). But in the database we suspect that ORACLE is turning varchar2(255) into a long because of it being a multibyte database. In the DOA code when it assigns the variables across it does a query.execute to get the types. This is the line thats falling over. This is before the code that changes strings to memos kicks in.
Can anyone shed any light on the issue, or how we may go about solving it, without changing the 10,000 or so TOracleDatasets we use over to using ftMemo (Long) ?
Cheers,
Cybrey
[This message has been edited by Cybrey (edited 14 January 2003).]
"can bind a LONG value only for insert into a LONG column"
on an execute with a TOracleDataset on a UTF8 database. The code worked perfectly on 8i. The code also works perfectly if the session property UseOCI7 set to true, this isn't really an option.
We think the error is occuring as Oracle 9.2i has tightened up its binding. The field type thats causing the problem is defined in Delphi as a ftString (String). But in the database we suspect that ORACLE is turning varchar2(255) into a long because of it being a multibyte database. In the DOA code when it assigns the variables across it does a query.execute to get the types. This is the line thats falling over. This is before the code that changes strings to memos kicks in.
Can anyone shed any light on the issue, or how we may go about solving it, without changing the 10,000 or so TOracleDatasets we use over to using ftMemo (Long) ?
Cheers,
Cybrey
[This message has been edited by Cybrey (edited 14 January 2003).]
