#987 closed bug (fixed)
PostGIS: zeros instead of NULLs in a table
Reported by: | msieczka | Owned by: | jef |
---|---|---|---|
Priority: | critical: causes crash or data corruption | Milestone: | |
Component: | Data Provider | Version: | Trunk |
Keywords: | Cc: | ||
Must Fix for Release: | Yes | Platform: | All |
Platform Version: | Awaiting user input: | no |
Description
- Add a numeric column to your PostGIS table (in QGIS or any other client).
- "Open Table" or "Identify Features" - see QGIS claims there are '0', instead of empty cells (NULL) in the column, although you did not enter them.
Actually these zeros are not there. These *are* NULL cells. Only QGIS displays them bogus.
This way you can't distinguish between cells really containing 0 and NULL. Moreover, you can't fill a NULL cell with a real 0 in QGIS - it will claim nothing changed in the table and won't let you save changes.
Change History (5)
follow-up: 3 comment:1 by , 15 years ago
comment:2 by , 15 years ago
Owner: | changed from | to
---|
comment:3 by , 15 years ago
Replying to msieczka:
#988 is related.
Also look at #962. https://trac.osgeo.org/qgis/attachment/ticket/962/nullprob.png illustrates the problem.
comment:4 by , 15 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
#988 is related.