Hi Andrea and Jukka, Big thanks for your quick responses.
@Andrea: tried your solution with no luck, I might probably design another id column in my table to keep tracking the features as Jukka mentioned @Jukka: Yes, I agree with you and I've seen the oddity before (can't remember what caused it, maybe invalid geometry). In fact, I am writing the python wrapper in the client side and control and validate the geometry input by use of some geometric library to generate the XML request document automatically. After having control on the input, so far I don't see that case happen again. But do you have a solution to the oddity? Cheers Deen -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Inserting-features-not-in-order-with-WFS-T-tp5314942p5314955.html Sent from the GeoServer - User mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
