On Thu, 1 Nov 2018 at 01:55, Baker, Matthew <matthew_ba...@dpsk12.org> wrote: > > Thanks again, Nyall. > > Re. 'only look in geometry columns' - no, we're not using this setting, nor > have we ever. Is that true that pre-3.4 was using that setting? I would have > imagined this is the other way around? I will see if this fix addresses this > issue when it gets implemented.
Pre 3.4 browser was ALWAYS using that logic, regardless of the connection's setting. So it would have been nice and fast, but missing tables which weren't present in the geometry_columns tables. (Note that QGIS automatically creates this table and populates it automatically during certain layer creation operations) Nyall > > Re. the schema display for dragging and dropping - still not a fan of this > feature - would prefer the QGIS browser window not be a DBA-type of GUI > (https://issues.qgis.org/issues/17719) but that's another issue altogether! > > Thanks again! > > -m > > > > > > -----Original Message----- > From: Nyall Dawson <nyall.daw...@gmail.com> > Sent: Tuesday, October 30, 2018 6:48 PM > To: Baker, Matthew <matthew_ba...@dpsk12.org> > Cc: Andreas Neumann <andr...@qgis.org>; qgis-user <qgis-user@lists.osgeo.org> > Subject: Re: [Qgis-user] Performance of MSSQL Server with QGIS 3.4 > > On Wed, 31 Oct 2018 at 01:28, Baker, Matthew <matthew_ba...@dpsk12.org> wrote: > > > > Thanks for the reply, Nyall. > > > > To clarify - this issue is just refreshing the database tree in the browser > > window - once refreshed (eventually), all tables behave normally (see below > > re. invalid geometries). > > > > 2.18 and 3.2 used to refresh the tables just fine. Upon installing 3.4, > > things have slowed down for all versions. > > Thanks for the clarification. Can you confirm whether you have the setting > "only look in the geometry_columns metadata table" switched on or off for > your connection? > > If you're not using this setting, then it's possibly related to this fix > https://github.com/qgis/QGIS/commit/e813fe880. Pre 3.4 QGIS was only looking > in the geometry columns table for the browser, and not respecting this > setting. > > > Another thing to note - 2.18 and 3.2 show only a handful of schemas in the > > database (not sure how it decides which one) - but now 3.4 is showing ALL > > schemas, including those without any tables and that weren't shown in > > 2.18/3.2 - that's weird! > > That's intended -- for db connections we should be showing empty schemas in > the browser, as this allows users to drag and drop tables into these schemas > to initially populate them. > > Nyall _______________________________________________ Qgis-user mailing list Qgis-user@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
