Re: [cx-oracle-users] Problem with internal buffer sizes
Brought to you by:
atuining
From: Anthony T. <ant...@gm...> - 2007-01-23 16:24:16
|
Currently only LOBs use the environment's "maxBytesPerCharacter" specification. Unfortunately (as far as I know -- please correct me if I am wrong) varchar2 buffers are limited to 4000 bytes and are specified in bytes, not characters. So you may be able to get away with increasing the buffer size for small strings but for large strings bad things will start to happen. :-) I'm not sure if there is a reasonable way around this or not. If anyone cares to enlighten me I'd be happy to learn. Anyone?? On 1/23/07, matilda matilda <ma...@gr...> wrote: > Hi all, hi Anthony, > > I have the following problem: > > The Oracle database I'm using has the internal encoding > WE8ISO8859P1. The frontend (shell, python) has the > default encoding UTF-8 (NLS_LANG=GERMAN_GERMANY.UTF8). > The Oracle client library is handling encoding convertion, BUT: > If I fetch a varchar2 (byte) column consisting of a character > that is encoded with two bytes in UTF-8, I get the following > error while fetching: > > cx_Oracle.DatabaseError: column at array pos 0 fetched with error: > 1406 > > I think it's a problem with internal buffers of the bind variables. > > 1) What can I do to get rid of that without changing NLS_LANG? > 2) Is there or probably will there a way to transparently circumvent > this problem. (automatic claiming of bigger buffers). > > Thanks in advance > Andreas Mock > > > > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > cx-oracle-users mailing list > cx-...@li... > https://lists.sourceforge.net/lists/listinfo/cx-oracle-users > |