Opened 15 years ago

Closed 15 years ago

Last modified 14 years ago

#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


  1. Add a numeric column to your PostGIS table (in QGIS or any other client).
  1. "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)

comment:1 by msieczka, 15 years ago

#988 is related.

comment:2 by jef, 15 years ago

Owner: changed from nobody to jef

in reply to:  1 comment:3 by cgsbob, 15 years ago

Replying to msieczka:

#988 is related.

Also look at #962. illustrates the problem.

comment:4 by jef, 15 years ago

Resolution: fixed
Status: newclosed

comment:5 by (none), 14 years ago

Milestone: Version 0.9.2

Milestone Version 0.9.2 deleted

Note: See TracTickets for help on using tickets.