[fdo-internals] SQL (Spatial) Azure

[Crispin_at_Linknode]

Hi,

We have put some research into the adaption of the SQLServerSpatial provider
to allow connections to SQL Azure hosted databases.

We currently have a build on x32 and x64 that can be used for Connection
(some) DescribeSchema and FeatureReader API calls and as such we can use the
provide within MapGuide to query and draw features - ya hoo!

A few things to air with the group before I get details written up:

 * Would a new RFC be required for SQL Azure support or is it a ticket "fix"

 * Should the embedded SQL code be unified - some of the limitations in SQL
Azure require changes that could either be kept as specific to an Azure
connection or the existing discovery SQL changed to be the same

 * At the moment it seems like some of the CreateSchema code is going to be
tricky - permissions between master and other databases.  This is not of
interest to us, so we are not looking at putting a lot of effort here...
does that limit the scope of a submission to getting into trunk

 * There is a really odd bug with spatial selection in MapGuide for
point-layers with our build of the provider- where the selected objects are
the *inverse* of an actual window selection (still need to see if that is
also in the 3.8 release version)

Many thanks - Crispin




--
View this message in context: http://osgeo-org.1560.x6.nabble.com/SQL-Spatial-Azure-tp5056652.html
Sent from the FDO Internals mailing list archive at Nabble.com.