A point definitely worth considering, but if you are inserting into an SHP or an SDF you shouldn't expect concurrent users as you need an exclusive lock on the file to do the write if I am not mistaken. If you have multiple users attempting to write to the same SDF or SHP you will likely experience problems including the example you show.
Of course with a database this should be a non-issue. Dave -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jason Birch Sent: Tuesday, October 09, 2007 12:34 PM To: MapGuide Users Mail List Subject: RE: [mapguide-users] How to get an auto-generatedIdafterInsertFeature ? I think that this might cause problems in high-concurrency situations: user a: selects max ID (23) user b: selects max ID (23) users a and b insert features user a: selects max ID (25) user b: selects max ID (25) ?? Jason -----Original Message----- From: Dave Wilson Subject: RE: [mapguide-users] How to get an auto-generated IdafterInsertFeature ? Another approach might be to select the Max Id before the insert and select the Max Id after the insert. I don't believe the Id's get assigned such that they will use existing gaps (from deleted features) so the new Id should always be higher correct? Dave _______________________________________________ mapguide-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapguide-users _______________________________________________ mapguide-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapguide-users
