You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Author Name: Manuel K (Manuel K)
Original Redmine Issue: 18583
Affected QGIS version: master
Redmine category:forms
Assignee: Alessandro Pasotti
Attribute of type integer;
DB: PostGIS
Allow NULL is checked; Editable
Minimum value: 2018; Maximum value: 2099; Step: 1
Problem:
In the form a NULL value is wrongly displayed as (Minimum value)-1 (i.e 2017) if "Representation for NULL values" in options was left empty (my preferred Setting). However, the value in the database is correct (NULL).
The described bug persists (master 3.3.0-71 and nightly 3.2.3-1).
And not only for attributes of type integer, but also for attributes of type numeric.
Example (type numeric):
Range widget configuration: Minimum: 0.00; Maximum: 399.90; Step: 0.10; Precision: 1; Allow NULL is checked.
--> In the form the NULL value is displayed as -0.1 (what corresponds to "[Minimum]-10^-[Precision]") instead of an empty field.
13303 was configured as representation_for_NULL_values_empty.jpg
Author Name: Manuel K (Manuel K)
Original Redmine Issue: 18583
Affected QGIS version: master
Redmine category:forms
Assignee: Alessandro Pasotti
Attribute of type integer;
DB: PostGIS
Allow NULL is checked; Editable
Minimum value: 2018; Maximum value: 2099; Step: 1
Problem:
In the form a NULL value is wrongly displayed as (Minimum value)-1 (i.e 2017) if "Representation for NULL values" in options was left empty (my preferred Setting). However, the value in the database is correct (NULL).
The text was updated successfully, but these errors were encountered: