Page 1 of 1
delphi 2010+odac 6.90.0.51 params as chinese string error!
Posted: Tue 15 Sep 2009 07:40
by xalion
version:delphi 2010
os version: win xp chinese
oracle version: oracle 10.2.0.4
direct mode:True
cx.SQL.Clear;
cx.SQL.Add('select * from XTB ');
cx.SQL.Add('where BZ=:bz and sysbz=''T''');
cx.Params[0].AsString:='abc';
cx.open;
It works fine.
cx.SQL.Clear;
cx.SQL.Add('select * from XTB ');
cx.SQL.Add('where BZ=:bz and sysbz=''T''');
cx.Params[0].AsString:='年份';
cx.open;
It show error!
Posted: Wed 16 Sep 2009 10:45
by Plash
Please specify the character set of your database, and the error message that you have received.
Posted: Wed 16 Sep 2009 14:32
by xalion
character set :ZHS16GBK
error:ORA01460:unimplemented or unreasonble conversion requested!
Posted: Thu 17 Sep 2009 09:11
by Plash
We have reproduced this problem, and we are working on it. You will be notified when we fix the problem.
Posted: Tue 13 Oct 2009 10:25
by Matt
Hi
I am looking at upgrading my odac components to version 6.90.0.51 using Delphi 2006.
Could you please tell me if this problem would exist in my version of delphi as we do have quite a few chinese customers that this could affect.
Many Thanks
Matt
Posted: Wed 14 Oct 2009 07:13
by Plash
This problem is fixed in ODAC 6.90.0.51.
Posted: Wed 14 Oct 2009 08:49
by azabluda
Hi Plash,
I'm keeping an eye on this ticket too, because we hit the same problem which DOES persist in 6.90.0.51 / C++Builder 2009. Did you mean some later build of 6.90.0.51 where "this problem is fixed"? I checked my registered user area today, but the bug is still there.
Thanks,
Alexander
Posted: Thu 15 Oct 2009 09:10
by Plash
This topic describes another problem (not related to OCIUnicode = True). Please see my reply to your e-mail regarding the problem with OCIUnicode.
Posted: Fri 16 Oct 2009 01:04
by xalion
with new 6.90.0.52. the1 bug is still there!!
Posted: Wed 28 Oct 2009 01:39
by xalion
when will you fix this bug?
Posted: Thu 29 Oct 2009 07:54
by Plash
We are planning to fix this problem in the next ODAC build.
Posted: Thu 26 Nov 2009 13:21
by Matt
Please can you confirm this problem is fixed in 6.90.0.53
Many Thanks
Matt
Posted: Fri 27 Nov 2009 01:31
by xalion
This bug is removed!