-
Notifications
You must be signed in to change notification settings - Fork 13
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
Problem with nastring for non-numeric columns #31
Comments
That would be for writing files, right? Do you think we need to also change something about reading? |
Frankly - for reading I would never create a missing when reading a A second best solution would be to treat empty string as missing (although I can imagine situations where However, I realize that all this is breaking so please decide what you think is best in the context of whole queryverse. |
Well, now is the time to break things! I haven't released the julia 1.0 version officially, and I'm willing to break things with that transition, and then hopefully not again for a long time (until we see julia 2.0). I think my own instinct would be to only return All of the reading logic is actually handled in TextParse.jl, so I'll have to figure out what the default there are... |
Good point - if all is quoted and only |
Because the default
nastring
isNA
there is a following problem:String
column with missing data in it;save
it to disk using default parameters; missings get converted toNA
on diskload
it back and you have"NA"
string where you earlier had missingsThe same problem occurs with e.g.
Char
data.While
NA
is a sensible default for numeric columns it is a bit confusing for non-numeric columns (and actually can lead to wrong results as it is fully possible to haveNA
string in data).I think that it would be best to have an empty string for missings in non-numeric data.
The text was updated successfully, but these errors were encountered: