Please note the ticket in question concerns usage of postgis via the OSGeo.OGR FDO provider and not the OSGeo.PostgreSQL provider.
I cannot determine from your post as to which provider you are actually referring to. I hope you are referring to the OGR provider so that I have only one problem to focus on instead of two. Also I didn't set the "low" priority on that ticket. That's just a probable oversight on the ticket OP's part. But I am in agreement about the true severity and it being a high priority item to resolve before MGOS 4.0 RC1 is released. - Jackie You wrote: Hi, sorry I didnt notice that there is already a ticket #2874 for this error. Let me know if there is something I can do to help to find the reason. I think the priority is not "low", we can not use MG 4.0 with this issue. -- *Please Note: I no longer create new posts or post replies to any OSGeo mailing list through nabble. As a result, you most likely won't see this message appear on nabble's view of any OSGeo mailing list and may only see this message through mailing list archives or depending on your mailing list subscription settings, through daily message digests or automated notifications from the mailing lists.*
_______________________________________________ mapguide-users mailing list mapguide-users@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/mapguide-users
