EDTFField fails to re-save fields without natural text field value #15
Comments
|
This is currently an issue for AGSA in particular because we are deliberately setting just the EDTF field on works without setting the corresponding |
jmurty
added a commit
that referenced
this issue
May 29, 2017
Improve performance of EDTFField when populating model instances from DB values by storing EDTF data in pickled format, not as string values that need to be re-parsed every time they are loaded. This implementation is naive and could be improved with a more sophisticated serialization approach for EDTF fields, though it works for now. This change also handles the issue in #15 where already- parsed EDTF field values are re-parsed when an instance is saved, unless there is a `natural_text_field` value present to override and reset the EDTF field value.
cogat
pushed a commit
that referenced
this issue
Jul 26, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If the
EDTFFieldvalue is set on a model instance and the instance is subsequently re-saved with an emptynatural_text_fieldvalue, thepre_savemethod fails because it tries to re-parse the existing EDTF field python value which is not a string.The text was updated successfully, but these errors were encountered: