[Qgis-user] bug in 3.10.2 (after upgrading from 3.10.1) with NULL being lost in PostGIS

[Jason Carlson]

Can anyone else confirm this before I submit it?

After I upgraded from 3.10.1 to 3.10.2 I noticed an issue that it no longer
handles null values correctly when updating records in PostGIS.

I rolled back to version 3.10.1 and the issue goes away.

Here is more detail:
I have some PostgreSQL tables that have fields that can be NULL or text but
I have check constraint in place saying it has to be NULL or one of a list
of specific strings.

In 3.10.1 if I go to edit a record that has some fields set as NULL, when
the QGIS attribute form loads for editing, it shows those fields as NULL
inside the text field (they can be text or null). I can make changes to any
fields and save and the NULL fields remain as NULL.

In 3.10.2 if I go to edit the same record, the QGIS attribute form when
displayed for editing the record does not show those fields as being NULL
but an empty string. When I submit changes, any fields that should still be
NULL are not being submitted as NULL as I get a check constraint error
saying it doesn't fit the criteria. I've tried entering into those fields
manually as NULL or 'NULL' or "NULL" and a dozen or so other guesses and it
still fails.

Again, if I roll back to version 3.10.1 it works as it has on many previous
versions all the way back to 2.8
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-user/attachments/20200204/7390b1b3/attachment.html>