[fdo-users] Define a SQL as source instead of a tablename (MySQL)

[Andy Morsell]

Why can't you accomplish this with the use of views in the database?  Also,
you might try creating a secondary join to the primary datasource
definition, but it will most likely perform more poorly than using a view. 


Andy Morsell, P.E.
Spatial Integrators, Inc.
http://www.SpatialGIS.com

-----Original Message-----
From: fdo-users-bounces at lists.osgeo.org
[mailto:fdo-users-bounces at lists.osgeo.org] On Behalf Of Alexander Bruch
Sent: Thursday, May 08, 2008 7:58 AM
To: fdo-users at lists.osgeo.org
Subject: [fdo-users] Define a SQL as source instead of a tablename (MySQL)


Hello,

is it possible or will it be possible in near future to provide a SQL as
datasource instead of using static tables? 

i.e. if i use mapguide studio to define a Layer, and i select a datasource,
than i can only choose Tables or views, which are defined in MySQL.

What i want is to enter a SQL, which should be used as Feature Source. 
It is not enough for me to define Queryfilters basedd on tables, because the
datasource (SQL) is build up on complex joins which includes userids. 

Is this possible in FDO?
Or is this just a missing feature in the Mapguide Server?

thank you for answer

Alexander Bruch
--
View this message in context:
http://www.nabble.com/Define-a-SQL-as-source-instead-of-a-tablename-%28MySQL
%29-tp17127289p17127289.html
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