#1023 closed bug (fixed)
0 is forced instead of null in Shapefile
| Reported by: | msieczka | Owned by: | jef |
|---|---|---|---|
| Priority: | critical: causes crash or data corruption | Milestone: | |
| Component: | Digitising | Version: | Trunk |
| Keywords: | Cc: | ||
| Must Fix for Release: | Yes | Platform: | All |
| Platform Version: | Awaiting user input: | no |
Description
- Create a new shapefile with 1 integer, 1 real and 1 string field.
- Digitize a single feature, don't fill the table.
*Each* fiels has value "0" forced, although you have not entered it. Editing table also does not let you have the cell empty; it force "0" as well.
I don't think it is a limitation of DBF - using DBF driver in GRASS I can have empty cells in the table, for any datatype.
Change History (4)
comment:1 by , 16 years ago
comment:2 by , 16 years ago
| Owner: | changed from to |
|---|
comment:3 by , 16 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
support for unset fields added in r8309
Note:
See TracTickets
for help on using tickets.
*Maybe* the bug is related to #987, #988, #962.