Ticket #2222 (closed bug: fixed)
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
Change History
Note: See
TracTickets for help on using
tickets.

