[fdo-users] Status of NVARCHAR Fields in ArcSDE Provider?
Romica.Dascalescu at autodesk.com
Fri Aug 27 10:53:53 EDT 2010
I know in the paste we had some issues with Unicode properties but we fixed them, see http://trac.osgeo.org/fdo/ticket/294
This changes was fixed in FDO 3.3 and it should work in FDO 3.4. ArcSDE supports Unicode only after 9.2 version.
In case the properties are GUID I think the support has been added in FDO 3.5.
From: fdo-users-bounces at lists.osgeo.org [fdo-users-bounces at lists.osgeo.org] On Behalf Of Crispin_at_1Spatial [crispin.hoult at 1spatial.com]
Sent: Friday, August 27, 2010 10:38 AM
To: fdo-users at lists.osgeo.org
Subject: [fdo-users] Status of NVARCHAR Fields in ArcSDE Provider?
Could anyone give me an update as to Unicode field support in the
latest/current ArcSDE providers.
I only have access to a Unicode DB at a couple of client sites with FDO 3.4
(which does not pick up the fields).
There was a discussion here last year (link below) and a sandbox for
development, but that got bogged down in GUID issues by the looks of it.
With ESRI setting the unicode flag to default on new databases it's going to
become a wider issue.
The recent work on RFC23 (http://trac.osgeo.org/fdo/changeset/5639) looks to
address some terrible performance problems when working with large corporate
datastores but is only half the story if wide text fields remain
Anyhow, just an update as to whether this has also been addressed would be
super, thank you!
View this message in context: http://osgeo-org.1803224.n2.nabble.com/Status-of-NVARCHAR-Fields-in-ArcSDE-Provider-tp5469714p5469714.html
Sent from the FDO Users mailing list archive at Nabble.com.
fdo-users mailing list
fdo-users at lists.osgeo.org
More information about the fdo-users