I've have closed the ticket 354 as invalid
Bruno
--
View this message in context:
http://www.nabble.com/Problem-in-the-GenerateFilter%28%29-method-of-the-MgSelection-class-tp14132755p20677720.html
Sent from the MapGuide Users mailing list archive at Nabble.com.
In your sample application, i've replace your URLEncode function ( witch is
using the escape function)
by encodeURIComponent and now your program runs properly without any errors
:)
Bruno
--
View this message in context:
http://www.nabble.com/Problem-in-the-GenerateFilter%28%29-method-of-the-Mg
I found the problem.
There is no error in the GenerateFilter command.
The error come while posting xml data from the client js to the server aspx
command.
Here and example of what's going on with FeatID = 250.
1) we get the XmlSelection from the Client API
+g==
2) we
Would GenerateFilters() the replacement for GenerateFilter() have this same
issue?
RFC 46: http://trac.osgeo.org/mapguide/wiki/MapGuideRfc46
The Rock
___
mapguide-users mailing list
mapguide-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/
I've been a little further on that problem
I have dupplicated the exacte same table ( the one in the demo attached)
On Oracle and PostGIS
So using the Autodesk.Oracle provider i don't have the bug.
After re-sequencing/Re-indexing GenerateFilter on Oracle works well
But i do have problem in PostG
This is very weird that nobody has ever notice that!
This bug is very blocking.
3 differents sdf and 3 different shp, all with the same problem, wow.
I'm going to try with a different provider, just to see!
IT really seems like a big bug, you know 256 is not a magic number!!!
Bruno
Patrick C
I just want to mention that this problem is really blocking because 1 out of
50 entities CANNOT be retrieved into an MgSelection. That means that I
cannot guarantee my clients that my applications are bug free because they
encountered this problem and I can't give them any bug fix. I hope somebo
