[fdo-users] RE: RE: RE: Unicode (nvarchar) support for MS SQL Server
max at geoinova.com
Sat Sep 15 11:08:49 EDT 2007
Although I'm using Autodesk Map 3D 2007 platform, I do not use neither Map's
libraries nor tools to create/access schemas, perform entity
checkin/checkout, stylization, etc. I developed my own set of tools and
functions to do that apart of Map's engine, using either Autodesk's or OSGeo
(native) FDO 3.2 providers available. Neverthless, my meta-model is fully
compatible with Map's.
As far as I can see, Map's MS SQL provider is responsible for this Unicode
problem. I'm new to MS SQL. Frankly, I don't want to mess with RDBMS layer
since it's FDO's business after all :-) Obviously, someone (for some reason)
decided to map String type to MS SQL's varchar type instead of nvarchar.
Now, despite the fact that Autodesk finally supports Unicode - I still can't
use it due to Autodesk's MS SQL FDO provider implementation decision. Bah
> I assume you are using the autodesk fdo schema products to create your
> schema. You will probably have to log a support incident with autodesk on
> the product you used to create the schema in mssql (map 3d?). It may be a
> matter of modidfying the schema and then reloading the data. Everything I
> can find mentions that changing the schema is most likely going to break
> metadata link. In other words the data and the metadata will be out of
> Perhaps explaining/describing what tools you used to create the schema and
> load the data would help.
> The autodesk support site is down for maint this morning so I am not
> much help from that. I did find the following... it may be a useful
> for you.
View this message in context: http://www.nabble.com/Unicode-%28nvarchar%29-support-for-MS-SQL-Server-tf4422980s18162.html#a12690840
Sent from the fdo-users mailing list archive at Nabble.com.
More information about the fdo-users