[mapguide-users] Joins using FDO SQL Server Spatial
martin.morrison at edsi.com
Thu Feb 12 09:46:47 EST 2009
The experience I had was that they were selectable, it just took a long time 3-4 minutes...
You will always get faster response with pre-canned data. Get the new SQL provider, process the geometry and the data into a single table and watch it fly.
From: mapguide-users-bounces at lists.osgeo.org [mailto:mapguide-users-bounces at lists.osgeo.org] On Behalf Of wordsy
Sent: Wednesday, February 11, 2009 4:35 PM
To: mapguide-users at lists.osgeo.org
Subject: [mapguide-users] Joins using FDO SQL Server Spatial
I have all my spatial and attribute data stored in an SQL Server 2008 GIS
enabled database. My table structure is as such. BaseTable (with base
attributes) and FeatureTable (with more detailed attibutes). I have created
views that join each FeatureTable with a BaseTable (1 to 1 relationship).
The FeatureTable has the Geometry datatype field in it.
The view created makes the layer unselectable on the map. But if I do a
view directly on the FeatureTable, the features are now selecteble.
My question is:
Can I not use inner joins (or any other joins) using this FDO (SQL Server
Spatial) ?? Anyone else run into this problem before?
Thanks in advance for any help.
View this message in context: http://n2.nabble.com/Joins-using-FDO-SQL-Server-Spatial-tp2311594p2311594.html
Sent from the MapGuide Users mailing list archive at Nabble.com.
mapguide-users mailing list
mapguide-users at lists.osgeo.org
More information about the mapguide-users