Alessandro Pasotti 38c91e4e97 [postgres] Fix checkPrimaryKeyUnicity option
This provider option was linked to the project level option
"Trust layer metadata..." which was implemented
to speed up loading of large dataset by trusting extent
read from metadata to avoid costly operations to determine
the layer extent.

Check PK unicity on the other hand has only effect on views
and query layers and it is useful as an independent
option to prevent loading of layers that have no PK (or the
wrong one).

But the operation of determine unicity of a values in a column
can also be costly, so better to get control back to the user.

Legacy default is preserved (the project-level "Trust..." option).

Fixes #21839

Funded by RAAB.nl
2019-04-24 17:14:42 +02:00
..
2018-10-08 05:03:49 +10:00
2019-01-08 11:50:35 +01:00
2018-10-08 19:16:29 +10:00
2018-09-14 15:33:57 +10:00
2019-04-07 15:35:43 +02:00