[gdal-dev] RFC 23: OGR Unicode

[Frank Warmerdam]

Tamas Szekeres wrote:
> Frank,
> 
> In the recent days we've also experienced similar problems with the
> OGR OCI driver. I suppose it might be related to the NCHAR or
> NVARCHAR2 columns, where the driver cannot figure out the proper
> length of the buffer to retrieve the field values. Therefore the OCI
> library always reports the following error:
> 
> ERROR 1: ORA-01406: fetched column value was truncated
> in OCIStmtFetch
> 
> Was this issue also addressed by this RFC or some additional changes
> should be made inside the driver? I couldn't find out how the driver
> will figure out the length of the buffers in these cases.

Tamas,

This RFC does not attempt to address multi-byte string parsing, or
manipulation issues.  I imagine we will need to deal with this
at some point in the future.

I imagine the OCI problem with sizing could be resolved by binding to
buffers 4x the stated column width.  Also, potentially some translation
would be required for NVARCHAR fields depending on what oracle does
by default.  I am *not* offering to address all these OGR drivers as
part of this RFC, but hopefully once the core services are supplied,
and OGR string fields are defined as UTF-8 it will be fairly straight
forward to fix these problems on a driver by driver basis.

If you don't want to fix this, file a ticket. Someone will be making
a pass through addressing Oracle issues in the coming months.

Best regards,
-- 
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up   | Frank Warmerdam, warmerdam at pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush    | President OSGeo, http://osgeo.org