-
Notifications
You must be signed in to change notification settings - Fork 50
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
Breaking changes with DataFrames master #61
Comments
Yes, good to track this! The original implementation of Query.jl actually used the |
Here's an interesting discovery: Query is providing a very handy method using DataFrames, Query #Both at master
df = readtable("something.csv") #Has a string column called LongNames with many characters
df[:ShortNames] = [n[1:4] for n in df[:LongNames]] This gives a no method error if Query is not included. Is this intended? I'm not sure this is a problem, but if this method is needed shouldn't it be in NullableArrays or Base? Just noting it here while mining issues in DataFrames master. |
I'v added lots of lifted versions of base methods for There is also some talk of creating a NullableOps package where these things could live until they are moved into base. |
See #62. |
@davidanthoff Amen to that, and thanks for putting them together. Is there a thread on a possible NullableOps package somewhere? I didn't see it on the mailing list or on google. |
|
I'm sure you're aware of this, but opening an issue to track. DataArrays was recently removed from DataFrames master and the default constructors now use Nullables.
using Query, DataFrames
This also breaks Query blocks and
@collect
:The text was updated successfully, but these errors were encountered: