Filter a layer based on FDO Autodesk Sql Server is impossible

[jleture]

Hi MapGuide developers,

I have a strange problem with MapGuide Enterprise 2009 (Update 1).

With the "FDO Autodesk SQL Server" provider, applying a filter on a layer throws an exception in the logs files ("AND and OR not supported in query when mixing property with spatial filters") when I tried to select an object in the AJAX viewer (or in the MapGuide Studio preview panel). Furthermore the filter doesn't apply on the layer, everything is visible so it's not good for privacy purpose.

With the very same data on MapGuide Enterprise 2008 (and version 3.2.x of FDO Autodesk Sql Server), it works perfectly!

Am I the only one having this problem with this provider?
Why a very common operation (filter a layer) works on MGE2008 and not MGE2009?
Too bad this driver is not open source...

Thank you. Edited by: julien.leture on Oct 30, 2008 6:58 PM

[gluckett]

Hi, I got around the FILTER issue by using the THEME as a filter.

Just add a new CONDITION and remove the default one. This is how I usually get around the FILTER issue.

regards
gordon

[gluckett]

Hi, I got around the FILTER issue by using the THEME as a filter.

Just add a new CONDITION and remove the default one. This is how I usually get around the FILTER issue.

regards
gordon

[jleture]

Hi gluckett,

Thank you very much for your answer.

I have made some tests and it's working!

I just don't understand why a filter throws an exception whereas a theme with the very same filter works fine.

This work around is perfect for an end-user, but with the API, MgFeatureQueryOptions::SetFilter method still fails if I add a filter. And if I don't add the filter, my query returns unwanted objects.

Anyway your tip is still very interesting.

Julien.