revisiting this problem; it is really making QGIS totally unusable for the large tables we are manipulating.
UNECESSARY FULL TABLE SCANS == VERY BAD USER EXPERIENCE!! If funds could be made available for this fix, is there anyone able/available to add this functionality, and avoid a full table scan on adding a layer, and on existing project start-up? (i.e. add a new pop-up dialog when one adds a new vector layer to optionally/manually enter the layer extents) this would make QGIS *-far-* more usable for “big data” thanks! Chris > this is my observation on 2.14.8: > > if the postgis layer is added (via the "add postgis layer" dialog) > with the "select at id" checkbox then when opening the attribute table > this is iterated one time. If the table is large browsing it is not > very snappy. > > If the layer is added without the "select at id" thing, then the table > is always iterated twice before opening. If the "show features visible > on map" option is selected, the table is still iterated twice (the > entire table, not only the records of visible features) before > opening. Browsing of large tables (once opened) is fast. > > One ticket I found that may be related > > http://hub.qgis.org/issues/10619 > > > cheers > > -- G -- > _______________________________________________ > Qgis-developer mailing list > [email protected] > List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Qgis-developer mailing list [email protected] List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
