Opened 15 years ago

Closed 14 years ago

#1238 closed defect (fixed)

Problem handling NULL values with SDF in 2.1 final

Reported by: ksgeograf Owned by:
Priority: low Milestone:
Component: Web API Version: 2.1.0
Severity: minor Keywords:
Cc: External ID:

Description

If a datasource has NULL values, it is impossible to read data from the Http interface.

See SDF file attached to ticket #1228.

Using the test page: http://localhost/mapguide/mapagent/selectfeaturesform.html

Attempting to read features gives: "Value for LUMINAIRETYPE property is null"

Attempting various ways to overcome this with a filter always returns an empty result set: LUMINAIRETYPE <> NULL LUMINAIRETYPE != NULL NOT LUMINAIRETYPE = NULL

It seems as if any filter returns an empty result set: LUMINAIRETYPE LIKE '*' LUMINAIRETYPE = NULL LUMINAIRETYPE > 5

The last one should give an error as LUMINAIRETYPE is a string column.

Perhaps the data is somehow broken, but it is possible to view the data by creating a FeatureSource and using the "Preview" function in Maestro/Studio.

Change History (3)

comment:1 by ksgeograf, 15 years ago

Hmm... Annoying... Trac has removed my linefeeds... Here it is with forced linefeeds:

If a datasource has NULL values, it is impossible to read data from the Http interface.

See SDF file attached to ticket #1228.

Using the test page: http://localhost/mapguide/mapagent/selectfeaturesform.html

Attempting to read features gives: "Value for LUMINAIRETYPE property is null"

Attempting various ways to overcome this with a filter always returns an empty result set:
LUMINAIRETYPE <> NULL
LUMINAIRETYPE != NULL
NOT LUMINAIRETYPE = NULL

It seems as if any filter returns an empty result set:
LUMINAIRETYPE LIKE '*'
LUMINAIRETYPE = NULL
LUMINAIRETYPE > 5

The last one should give an error as LUMINAIRETYPE is a string column.

Perhaps the data is somehow broken, but it is possible to view the data by creating a FeatureSource? and using the "Preview" function in Maestro/Studio.

comment:2 by jng, 15 years ago

Possibly related: #708

comment:3 by jng, 14 years ago

Resolution: fixed
Status: newclosed

Fix for #708 fixes this

Note: See TracTickets for help on using tickets.