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
my field, another field, third field
value 1, value 2, value 3
That this will create fields named " another field" and " third field".
In the grid view, it is not possible to sort or search on either of those fields. I assume using the API it would also not be possible to sort on those fields (though search should work).
The problem
Parts of the code does not trim field names (for instance the datapusher, and the datastore_create API); however other parts of the code does trim field names (for instance the code that splits a sort string: " another field, third field" becomes ['another field', 'third field'])
A solution
Given that there is no practical use for having field names that contain leading or ending spaces, I suggest the datastore API should trim field names.
The text was updated successfully, but these errors were encountered:
Now that #1971 has been merged, it will not be possible to insert new data with fields that start/end with whitespaces. So this issue now only affects already uploaded data.
How to reproduce
Upload the following CSV to the Datapusher:
my field, another field, third field
value 1, value 2, value 3
That this will create fields named " another field" and " third field".
In the grid view, it is not possible to sort or search on either of those fields. I assume using the API it would also not be possible to sort on those fields (though search should work).
The problem
Parts of the code does not trim field names (for instance the datapusher, and the datastore_create API); however other parts of the code does trim field names (for instance the code that splits a sort string: " another field, third field" becomes ['another field', 'third field'])
A solution
Given that there is no practical use for having field names that contain leading or ending spaces, I suggest the datastore API should trim field names.
The text was updated successfully, but these errors were encountered: