Ticket #2141 (closed defect: fixed)
Handling of DBF NULL values
|Reported by:||unicoletti||Owned by:||sdlime|
The dbf code in mapserver does not handle correctly null numeric values (and possibly other types too, though I haven't checked) and returns ************ which is the internal dbf representation for a null value. This has undesired side effects on filters and leads to parse errors which are translated in exceptions in java mapscript eventually blocking the generation of the map.
As an example implementation see the DBFIsAttributeNULL() in shapelib/dbfopen.c