Hi Régis,
The trust option is used in QgProject with
QgsVectorLayer::setReadExtentFromXml
https://github.com/qgis/QGIS/blob/master/src/core/qgsproject.cpp#L3304
Then in the case of a postgres layer, the checkUnicityKey is disabled
https://github.com/qgis/QGIS/blob/master/src/core/qgsvectorlayer.cpp#L1684
And it's all. The trust option only avoid to calculate layer Extent and
verify primary key for postgres layers.
The estimatedMetadata layer option is more common in provider. It will
be great to can check/uncheck this option.
Regards
René-luc
Le 19/03/2020 à 19:30, Régis Haubourg a écrit :
Hi, can someone explain what is the real logic currently coded for
trust option? It feels like this topic raises again each year for 5
years now, and we have regressions and what it is supposed to do.
It was funded at start to not check at all any metadata on the
datasource and read only qgs informations
Did it change for some reason ? Why?
It should be adequate even for big databases of QGIS stores all the
required informations.
Regards
Regis
_______________________________________________
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
