You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Test replacementVersionHasNoSuccessor randomly selects a feature and replaces it with a new feature (replace request).
When the new feature is generated the attribute gml:id is set to "id-CURRENTTIMESTAMP".
Then, the replace statement is created using a filter expression with the previously generated gml:id.
Of course, a feaure with the gml:id containing a timestamp does not exist.
Instead, the original gml:id (without timestamp) should be used for the filter expression of the replace request.
The text was updated successfully, but these errors were encountered:
dstenger
changed the title
Test replacementVersionHasNoSuccessor (Feature versions) sets wrong attribute value for gml:id
Test replacementVersionHasNoSuccessor (Feature versions) sets wrong attribute value for gml:id in filter expression
Oct 17, 2016
The first transaction request sets a dummy feature id and the server reports the assigned id in the response; this server-generated id (@Rid) is then extracted and included in the subsequent query to fetch the NEXT version, which shouldn't exist because the given id should correspond to the LATEST version.
Is this not the case? What error message is produced?
The problem is that the feature id was set to a dummy id. This is not expected as the gml:id cannot be altered except by an insert request (see F.4 Identifiers in WFS 2.0). Sure if feature versioning is enabled, a replace results in creating a new latest version (15.2.6 Replace action, WFS 2.0). But this is done by the server side, so that the client must not change the gml:id. The already existing replace-Tests in the Transaction CC also uses the original feature with the original feature id.
Setting the feature id to a dummy id causes an unexpected request, cause the the dummy id is used in the filter (and a feature with this id does not exist):
Test replacementVersionHasNoSuccessor randomly selects a feature and replaces it with a new feature (replace request).
When the new feature is generated the attribute gml:id is set to "id-CURRENTTIMESTAMP".
Then, the replace statement is created using a filter expression with the previously generated gml:id.
Of course, a feaure with the gml:id containing a timestamp does not exist.
Instead, the original gml:id (without timestamp) should be used for the filter expression of the replace request.
The text was updated successfully, but these errors were encountered: