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.

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

Discover on Mongo shouldn't engage discovery heuristics on values #105

Open
mrocklin opened this issue Feb 24, 2015 · 0 comments
Open

Discover on Mongo shouldn't engage discovery heuristics on values #105

mrocklin opened this issue Feb 24, 2015 · 0 comments
Milestone

Comments

@mrocklin
Copy link
Member

When we interact with Python data we use full heuristic mode. This does things like say that discover('1.0') == float64. This is appropriate when we guess the datashape of data in text files like CSV. This isn't appropriate when we grab data from Mongo which is already somewhat typed. In these cases a string is a string and we shouldn't do any guess work.

Perhaps the dual meaning of discover should be made more explicit.

@cpcloud cpcloud modified the milestones: 0.3.1, 0.3.2 Mar 6, 2015
@cpcloud cpcloud modified the milestone: 0.3.2 Mar 19, 2015
@cpcloud cpcloud modified the milestone: 0.4.0 Jun 27, 2015
@cpcloud cpcloud modified the milestones: 0.4.0, 0.3.5 Oct 5, 2015
@cpcloud cpcloud modified the milestones: 0.4.0, 0.4.1 Dec 4, 2015
@kwmsmith kwmsmith modified the milestones: 0.4.1, 0.4.2, 0.5.0 Feb 2, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants