Bug report #18255

Database configurations not carried over to QGIS 3.0

Added by rmercer - about 6 years ago. Updated about 6 years ago.

Affected QGIS version:3.0.0 Regression?:No
Operating System:Windows 7 Pro Easy fix?:No
Pull Request or Patch supplied:No Resolution:
Crashes QGIS or corrupts data:No Copied to github as #:26146


My data is stored in a Postgres database. I had a number of configurations stored for different usernames and databases. These are no longer in the DB Manager in QGIS 3.0. Some additional information is that when I upgraded to 3.0, I ended up having to completely remove my previous OSGeo4W directory because there were legacy files remaining that were causing errors with the new install. I do not know where the configuration information is stored, so it may have been removed when I did the clean install. One way or the other, it would be helpful to document the instances where a clean install is necessary, and include a reminder that your DB config information will be lost.

Adjunct to this is the fact that existing Postgres layers in a project have no reference to the database they came from. If you select "Update SQL Layer" in the layer context menu, all the layers are listed as Virtual layers. There is no reference to the database they are loaded from, or any means of modifying the source.

qgis-bin_2018-02-27_11-43-08.png - Existing Postgres layers listed as Virtual Layers (116 KB) rmercer -, 2018-02-27 08:44 PM


#1 Updated by Giovanni Manghi about 6 years ago

  • Status changed from Open to Feedback

Are the connections carried over in the QGIS browser (are they just missing in DB Manager?)?

#2 Updated by rmercer - about 6 years ago

They are not carried over anywhere. No connections are listed in the Browser even though the layers in the screenshot are active Postgres layers.

#3 Updated by Giovanni Manghi about 6 years ago

  • Status changed from Feedback to Open
  • Category changed from DB Manager to Unknown

Also available in: Atom PDF