Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Import, correct handling of nullable fields #183

Closed
lat9 opened this issue Jan 1, 2021 · 0 comments
Closed

Import, correct handling of nullable fields #183

lat9 opened this issue Jan 1, 2021 · 0 comments
Labels
bug fix provided
Milestone
v1.6.5

Comments

@lat9
Copy link
Owner

lat9 commented Jan 1, 2021

Currently, if a numeric field-type has a default of NULL there is no way to force that value back to its default. In addition, an export with those null-defaulted fields provides an empty string for the field-value, causing an error when the export is re-imported.
@lat9 lat9 added the bug label Jan 1, 2021
@lat9 lat9 added this to the v1.6.5 milestone Jan 1, 2021
lat9 added a commit that referenced this issue Jan 1, 2021
@lat9
#183: Correct handling of nullable integer, float and enum fields.
9881c5d
@lat9 lat9 closed this as completed Jan 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug fix provided
Projects
None yet
Milestone
v1.6.5
Development

No branches or pull requests
1 participant
@lat9