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
On Tue, Feb 4, 2020 at 5:02 PM Jason Carlson
wrote:
> Can anyone else confirm this before I submit it?
>
Can you please check latest master builds first? I've done a couple of
fixes in the past few days that might have an impact on this issue.
If the issue is still there, please file a ticket
Hi Alessandro,
Thanks for your response.
I've only used the standalone installers so it took me a bit to figure out
how to start QGIS when using the OSGeo4W installer. My standalone was
version 3.10.2-0 and in the OSGeo4W installer I see a 3.10.2-2 as well as
the development version of 3.11.0-72.
Hi Jason,
the quickest way to test current master for your case is to unzip the
latest build artifact for windows 64bits (it's a zip inside a zip) on your
PC and launch the qgis.exe binary you find inside.
No installation is required and it's completely standalone, there is no
Python but you don't
It works great. I'll just roll back to the standalone 3.10.1 until they are
in the next version. Thanks :)
*Jason*
On Tue, Feb 4, 2020 at 1:36 PM Alessandro Pasotti
wrote:
> Hi Jason,
>
> the quickest way to test current master for your case is to unzip the
> latest build artifact for windows 6
