It's actually both MapGuide and FDO related. There's 2 problems here: 1. There's definitely a bug in the SQL Server FDO provider. The insert command (transactional or not) actually succeeds, but it blows up trying to get the class definition from the feature reader that is returned by FdoIInsert::Execute(). The Execute() call itself doesn't throw an exception. If you did this code with raw FDO, I'm certain you'll get the same result.
2. If transactions are involved, it's even worse. Transaction rollback doesn't even happen, the active transaction is left dangling due to faulty exception handling! I made a ticket for this (http://trac.osgeo.org/mapguide/ticket/2165). The fix for this is simple. So file the FDO bug, as that's the root problem. Fixing problem #2 doesn't solve problem #1 - Jackie -- View this message in context: http://osgeo-org.1560.n6.nabble.com/Error-on-insert-features-into-SQL-Server-Spatial-tp4987600p5013278.html Sent from the MapGuide Users mailing list archive at Nabble.com. _______________________________________________ mapguide-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapguide-users
