#988 closed bug (fixed)
PostGIS: allow NULL in numeric columns
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
Change History (4)
comment:1 by , 15 years ago
Owner: | changed from | to
---|
comment:2 by , 15 years ago
comment:3 by , 15 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
The problem with saving the null values is when sending the INSERT or UPDATE statement to the PostgreSQL database the value is quoted, which is okay for numbers and must be for special values like 'NAN' or 'Infinity', but quotes with zero or more spaces is not accepted. The value needs to be NULL (no quotes) or the comma separators with nothing but whitespace between.