Updating to QGIS Browser instead of DB Manager

[wildintellect]

These are notes from testing if the Workshop can be done without the DB Manager. The short answer is yes, with minor updates to the content. I did not list out all the things that need to be updated but rather noted the likely stumbling blocks that could be confusing and how to get around those.

Data Source Manager Spatialite bugs

These should be reported to QGIS

• New button links to Connection dialog
• Connections doesn't list all databases that Browser has added

For the workshop we'll just rely on the Browser window instead and ignore the Data Source Manager

Workshop

Data loading

1. Do you always have to load the data in QGIS before importing to DB?
   No, the Processing toolbox can do it because it has a File load ... instead of a preloaded layer. We'll note this is an advanced method for large imports that will let you bypass loading the full data in the map. For the workshop we can keep it as is, loading the shp first.

2. Layer and Column names

   1. default unique ID is pk no id, either override on import or update workshop
   2. Table names also need to match, watersheds is not the original name

SQL

• You have to Refresh Broswer after RecoverGeometry on a new spatial table for the browser to realize it's spatial
• Note loading the Spatial Join query has 24,000 features so it takes a while to load on the fly "Viewing a Query to QGIS" , we could add a limit or filter to reduce the data if we want.