[fdo-users] RE: RE: RE: RE: Unicode (nvarchar) support for MS SQL Server

[Maksim Sestic]

Brad,

You're right. As far as I can see, there are two solutions to this (both
maintained by FDO):

1) Introduce an extra parameter to DataStore Create command to let users
decide whether strings get stored as Unicode or non-Unicode (non-Unicode =
default RDBMS setting). Then add appropriate Capability property to test
whether datastore supports Unicode at all.

2) Let users explicitly set FdoType-to-RdbmsType mapping. I guess this one
is hard to implement by both FDO core and providers, and doesn't seem viable
solution. It actually breaks FDO abstraction guidelines.

Regards,
Maksim Sestic



bradgisoklah wrote:
> 
> I agree Maksim,
>   I asked for this to be repaired in the opposite direction in the arcsde
> provider because my "vendor" decided that all fields would be Unicode. And
> the provider didn't support that. BTW: Unicode numeric fileds don't change
> the character set drastically) You need to be able to turn it on in your
> schema. It would be nice if the providers had a mechanism to support it
> either way. I don't really understand how you loaded your data. But I do
> know that it is at the data load that it must occur. Field types schema
> changes cannot occur on most rdbms's with data residing tin the field. And
> then the provider needs to be able to handle it after that.
> 
> 
> 
> -----Original Message-----
> From: fdo-users-bounces at lists.osgeo.org
> [mailto:fdo-users-bounces at lists.osgeo.org] On Behalf Of Maksim Sestic
> Sent: Saturday, September 15, 2007 10:09 AM
> To: fdo-users at lists.osgeo.org
> Subject: [fdo-users] RE: RE: RE: Unicode (nvarchar) support for MS SQL
> Server
> 
> 
> Brad,
> 
> 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
> :-)
> 
> Regards,
> Maksim Sestic
>  
> 
> 
> bradgisoklah wrote:
>> 
>> ...
>> 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
>> the
>> metadata link. In other words the data and the metadata will be out of
>> sync.
>> 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
>> getting
>> much help from that. I did find the following... it may be a useful
>> contact
>> for you.
>> http://discussion.autodesk.com/thread.jspa?threadID=523657
>> Brad
>> 
> 
> -- 
> View this message in context:
> http://www.nabble.com/Unicode-%28nvarchar%29-support-for-MS-SQL-Server-tf442
> 2980s18162.html#a12690840
> Sent from the fdo-users mailing list archive at Nabble.com.
> 
> _______________________________________________
> fdo-users mailing list
> fdo-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/fdo-users
> 
> _______________________________________________
> fdo-users mailing list
> fdo-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/fdo-users
> 
> 

-- 
View this message in context: http://www.nabble.com/Unicode-%28nvarchar%29-support-for-MS-SQL-Server-tf4422980s18162.html#a12731486
Sent from the fdo-users mailing list archive at Nabble.com.