Or let's re-frame this question.
Were the terrible feature joins in the past involve a SDF or SHP source on
the left side? This was the side that MapGuide said was not sortable and
thus you got the worst performing (and buggiest) join algorithm.
Now, as long as the join is on a single property, M
The provider says it can sort. So yes.
- Jackie
--
View this message in context:
http://osgeo-org.1560.n6.nabble.com/Number-Format-tp4716006p4880563.html
Sent from the MapGuide Users mailing list archive at Nabble.com.
___
mapguide-users mailing list
m
Hi Jackie,
does this include ODBC?
--
View this message in context:
http://osgeo-org.1560.n6.nabble.com/Number-Format-tp4716006p4879781.html
Sent from the MapGuide Users mailing list archive at Nabble.com.
___
mapguide-users mailing list
mapguide-users
In-memory Feature Joins aren't as terrible now for 2.4. As long as both sides
are sortable (which is the case for the majority of FDO providers), you'll
get the best performing algorithm.
- Jackie
--
View this message in context:
http://osgeo-org.1560.n6.nabble.com/Number-Format-tp4716006p485745
Thanks Jackie,
I think this would be a great addition to MapGuide.
Although I tend to just point to a web page for all my tooltips (to avoid
awful joins)
I do like to use Maestro to create traditional tooltips and the number
format would be very handy.
--
View this message in context:
http:/
FDO could use with some more expression functions like this, even if there is
no native support for them from the provider and we have to go through the
slower FDO Expression Engine to use them.
- Jackie
--
View this message in context:
http://osgeo-org.1560.n6.nabble.com/Number-Format-tp4716006
