Can't check in multiple features created in mysql

[gregboone]

1. Launch AutoCAD Map 2009 and create a new drawing
   
2. Create a SHP connection and load a set of point data
   
3. Create a FDO connection to a MySQL Server
   
4. New a mysql datastore, specify the coordinate system as CA83IIIF
   
5. Bulk copy data from SHP to the new MySql data source
   
6. Select MySQL connection in FDO, and add the data to the map
   
7. Right click the layer in Display manager, select Create -> Create New Multipoint school_private_pts
   
8. Create three points in the map and press Enter
   
9. Click check in toolbar button to check in the new features
   

Result: Error message appears, Feature was not saved in the target feature source. Failed to insert feature. Shape type mismatch on geometric property 'Geometry' of the feature class 'school_private_pts'.

Expected: New features shall be checked in.

[gregboone]

This defect has its origins in the manner in which the the AutoCAD map specific bulk copy process reads schema definitions from a shape file and creates the resulting schema in MySQL. Since the origin of the schema is a shape file, there is a limitation on the types of Geometry that can be created for a specific Shape table. For instance, if the Geometric Type is Point and the Specific Geometry SubType is Point in the Shape file, this restriction will be carried forward to the schema definition created in the MySQL data store. However, once a user has bulk copied data from Shape to MySQL, there is an implied expectation that the user will be able to perform an insertion of a multi-point feature due to the fact that MySQL does support multi-point geometry. The Map DataManager UI reflects this expectation by displaying both the ‘Create Point’ and ‘Create Multi-Point’ options. This expectation will not be honored by the MySQL provider because the provider provides an extra level of checking that determines if the geometry subtypes match. If they do not, an exception is thrown. This level of checking is only performed in the MySQL and PostGIS providers and is not present in the other RDBMS or SDF providers. Therefore, it is prudent to relax the check in the MySQL provider so that it remains consistent with the other FDO providers.

[gregboone]

Refer to r3705