Hi,
This one is due to an inconsistency in handling uniqueidentifier columns by the SQLServerSpatialProvider. When the schemas are read, the column is recognized and mapped to a property definition. However, the FdoISelect command implementation does not recognize this column type.
Has a trac ticket been logged for this one yet? If not, I could create one.
Brent.
-----Original Message-----
From:
[hidden email] [mailto:
[hidden email]] On Behalf Of Jason Birch
Sent: Monday, February 02, 2009 1:15 PM
To: FDO Internals Mail List
Subject: [fdo-internals] Known SQL Spatial bug?
http://tinyurl.com/b3tjzkLooks like they were having problems with uniqueidentifier column type.
Jason
_______________________________________________
fdo-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-internals_______________________________________________
fdo-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-internals
