Ticket #2222 (closed bug: fixed)

Opened 4 years ago

Last modified 4 years ago

properly handle null attribute values in WFS update

Reported by: tschaub Owned by: tschaub
Priority: minor Milestone: 2.9 Release
Component: Format.WFST Version: 2.8
Keywords: Cc:
State: Complete

Description (last modified by tschaub) (diff)

Currently, if a feature attribute value is null (e.g. {foo: null}), we write something like:

<Property>
    <Name>foo</Name>
    <Value></Value>
</Property>

This should look like the following:

<Property>
    <Name>foo</Name>
</Property>

An attribute with a null value should not show up in an insert. An attribute with an undefined value should not show up in insert or update.

Attachments

2222.patch Download (2.5 KB) - added by tschaub 4 years ago.
properly handle null and undefined attribute values

Change History

Changed 4 years ago by tschaub

  • description modified (diff)

Changed 4 years ago by tschaub

  • description modified (diff)

Changed 4 years ago by tschaub

properly handle null and undefined attribute values

Changed 4 years ago by tschaub

  • state set to Review

Tests pass (in FF3). Thanks for the review.

Changed 4 years ago by ahocevar

  • state changed from Review to Commit

Very nice! Tests also pass in IE7. Please commit.

Changed 4 years ago by tschaub

  • status changed from new to closed
  • state changed from Commit to Complete
  • resolution set to fixed

(In [9615]) Proper handling of null and undefined attribute values in WFS transactions. r=ahocevar (closes #2222)

Note: See TracTickets for help on using tickets.