You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Duplicate policy on QgsFields when duplicate features
PR Description:
Description
On duplicating a feature (and it's children) the duplicate policy will be concerned for fields. There are three options:
Default is "Duplicate Value".
A good use case where this is useful is on a timestamp as default value, when this feature has been created (means duplicated).
Technical info
This functionality is implemented the same way than the split policy, although the split policy is based on the policy of the field domain (if available) what means it concerns the OGRFieldDomainSplitPolicy. This is not part of the duplicate policy. The duplicate policy only concerns the QgsFields and is configured over the attribute form properties.
Still I named the enum FieldDomainDuplicatePolicy - because maybe one time the OGR api offers this policy as well and with this we can use it the same way.
That's why it's named FieldDuplicatePolicy.
Commits tagged with [need-docs] or [FEATURE]
The text was updated successfully, but these errors were encountered:
Request for documentation
From pull request qgis/QGIS#57217
Author: @signedav
QGIS version: 3.38
Duplicate policy on QgsFields when duplicate features
PR Description:
Description
On duplicating a feature (and it's children) the duplicate policy will be concerned for fields. There are three options:
Default is "Duplicate Value".
A good use case where this is useful is on a timestamp as default value, when this feature has been created (means duplicated).
Technical info
This functionality is implemented the same way than the split policy, although the split policy is based on the policy of the field domain (if available) what means it concerns the
OGRFieldDomainSplitPolicy
. This is not part of the duplicate policy. The duplicate policy only concerns the QgsFields and is configured over the attribute form properties.Still I named the enumFieldDomainDuplicatePolicy
- because maybe one time the OGR api offers this policy as well and with this we can use it the same way.That's why it's named
FieldDuplicatePolicy
.Commits tagged with [need-docs] or [FEATURE]
The text was updated successfully, but these errors were encountered: