Hi Jukka,
I tried to improve this problem in r4343
1) I think OpenJUMP must handle null values because
- null values are supported in all databases
- null values is different from empty string, false or 0 in the OpenJUMP
API itself
2) text based format will generally not support or have a bad
Hi,
Actually it look like dBase III does not support NULL strings and using empty
characters instead when saving is the right thing. It is also used like that in
http://shapelib.maptools.org/dbf_api.html
" Note that NULL fields are represented in the .dbf file as having all spaces
in the fiel
Hey,
that's interesting.
The STRING data type also supports NULL. However if one saves this
attribute data into a Shapefile/dBASE and reopens this file, then all
strings will change from NULL to "".
From this perspective it is interesting, that Shapefiles actually
support NULL. I guess it must b
Hi Jukka,
Good point about nullable Boolean.
I'd like to keep the checkbox, rather than a 3 items combobox,
but I think it will be difficult to add the capability to "nullify" it.
Notice that boolean type is not the only one concerned.
Once you have set a value for a String attribute type, you ca
Hi Michael,
Have you been thinking if OpenJUMP should support NULL as a third option in
Boolean attributes? Right now it seems to partly support NULLs, partly not.
- Create a new feature, do not edit attributes, save -> Boolean
attributes are saved as NULLs but user probably believes
