On mardi 21 mars 2017 09:24:13 CET Andrea Aime wrote:
> On Tue, Mar 21, 2017 at 5:45 AM, Dave Blasby <dbla...@boundlessgeo.com>
>
> wrote:
> > I was looking at the WFS-T response for Inserts (it's a list of FIDs).
> > The spec says these should be in the same order as the features in the
> > request's Insert elements.
>
> I never heard of this requirement so I went and check, indeed all 3 spec
> say so. However, it seems that at least the old
> WFS CITE test we're running did not verify that.
>
> So, you're not seeing things, but I believe you're the first one to care
> about it enough to report the problem
Well, getting out of order IDs would certainly mess up things in the QGIS WFS
client when
doing multiple inserts at once, especially if doing later updates of the
features (the wrong
feature would be modified on the server)
I'm surprised this wasn't raised before, but I can see we have this logic :
/* Fix issue with GeoServer and shapefile feature stores when no real
feature id are returned but new0 returned instead of the featureId*/
Q_FOREACH ( const QString &v, idList )
{
if ( v.startsWith( "new" ) )
{
reloadData();
return true;
}
}
which makes that we don't trust such Ids and have to re-issue a GetFeature
request. But if the
ids do not start with "new", we would have the issue.
Even
--
Spatialys - Geospatial professional services
http://www.spatialys.com
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
