-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
QGIS 3.10 - Unable to load layers from PostgreSQL 12 / PostGIS #32716
Comments
@andy-harney this has been recently fixed in master, please give it a try. |
Hi @gioman I can see that it looks fixed in 6c9f01e. Unfortunately I don't have an environment set up to build QGIS. Am I correct in saying that this fix will be included in the next point release on the 22nd November? Thanks. |
Best to check it in weekly builds: So that you can report back before the release. |
@andy-harney 6c9f01e it's a Python only patch, you can quickly change the plugin python code on your machine without the need to rebuild anything. |
Hi @elpaso |
@andy-harney thank you for the feedback, I'll have a look. |
@elpaso Thank you. 👍 |
Not currently - master in x86_64 has been too large for a NSIS package for a while - that'll will change once GRASS doesn't depend on python2. But the weeklies (as all other of our standalone installer) are snapshots of OSGeo4W - so what's not there, won't be in the weeklies either. |
That's misleading. 1c1ceb1 was in #32463 and that was merged into master 2 days ago.
yes. |
@andy-harney I cannot reproduce it on master: I can add layers from PG 12 through the data source select dialog without problems, can you check the message logs and see what exactly the error is? Or send me a DB dump of the table that does not open? |
Hi @elpaso , Here is the paste from logs. Below is the connection window showing the test connection succeeds then a gif of the process I'm following. This is from qgis-dev from OSGeo4W, QGIS code revision 1c1ceb1
Thanks again. |
Fixes qgis#32716 in PG provider
Unfortunately there are still a lot of bugs in DB manager related to changes in the way definitions can be retrieved, but this patch fixes the constraint issue in the provider side. My test case (on both version 10 and 12):
try that on PG 10, and PG 12 in DB manager and see what I mean |
Yeah, I'm pretty certain that its just the retrieval of layers/tables from the data source manager that's causing the most immediate issues. Existing QGZ files with layers in pulled from PostgreSQL 12 open and work fine. Thanks for looking into this. |
I can confirm that this is fixed in nightly builds of 3.11 |
Describe the bug
Connecting to a PostgreSQL 12 DB works fine, but trying to load layers results in the following error.
I believe this is linked to the same issue reported against GDAL here OSGeo/gdal#1692
The GDAL version shipped with QGIS 3.10 is 2.4.1, which does not play nice with PostgreSQL 12.
QGIS and OS versions
QGIS 3.10 code revision 6c816b4
Windows 10
PostgreSQL 12
PostGIS 3
Additional context
I think this issue #32558 is the same.
The text was updated successfully, but these errors were encountered: