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

Bug: CategoricalReader assumes that the fieldtype metadata is not a tuple #126

Open
atbenmurray opened this issue Mar 25, 2021 · 0 comments
Open

Bug: CategoricalReader assumes that the fieldtype metadata is not a tuple #126

atbenmurray opened this issue Mar 25, 2021 · 0 comments
Assignees
@atbenmurray

Comments

@atbenmurray
Copy link
Member

atbenmurray commented Mar 25, 2021 •
edited
Loading

However, it typically is. Other readers work around this by performing a split on comma following by selection of the first element. CategoricalReader did not get this, for some reason
@atbenmurray atbenmurray self-assigned this Mar 25, 2021
@atbenmurray atbenmurray changed the title Bug: CategoricalField assumes that the fieldtype metadata is not a tuple Bug: CategoricalReader assumes that the fieldtype metadata is not a tuple Mar 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@atbenmurray atbenmurray

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@atbenmurray