-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow field customisation when importing db tables #60940
Conversation
Previously the widget would always just use a generic hardcoded list of field types. This isn't appropriate for all destination providers, which may not support certain field types. Add API so that an explicit list of supported destination field types can be set for the widget, restricting the choices available to users for destination fields.
Implement fallback logic, so eg if the destination field types don't support one of the input types exactly, we can still make reasonable matches to a compatible field
Allows remapping fields from the source fields, including specifying the exact output field type, and source expression
This expands the database table import dialog to add a new field mapping section, which gives users control over the fields in the created table. Users can rename, set the exact destination field types, and tweak the source expression for each output field. Fields can also be excluded from the import, or new fields created which don't exist in the source table. Sponsored by City of Canning
This pull request has been tagged for the changelog.
You can edit the description. Format available for credits
Thank you! |
@nyalldawson A documentation ticket will be opened at https://github.com/qgis/QGIS-Documentation when this PR is merged. Please update the description (not the comments) with helpful description and screenshot to help the work from documentors. Thank you! |
🪟 Windows Qt6 buildsDownload Windows Qt6 builds of this PR for testing. 🪟 Windows buildsDownload Windows builds of this PR for testing. |
@nyalldawson |
This expands the database table import dialog to add a new field mapping section, which gives users control over the
fields in the created table. Users can rename, set the exact destination field types, and tweak the source expression
for each output field. Fields can also be excluded from the import, or new fields created which don't exist in the source table.
Refs #24192
Refs #45286
Sponsored by City of Canning