-
Notifications
You must be signed in to change notification settings - Fork 20
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
Add support for int64
results
#6
Comments
Hi, I'm having the following problem (using dbplot_0.2.1.9000), which seems related to this issue:
Any thoughts on why this is happening? |
After looking at the PR that fixed this and later commits, seems this has been reverted? |
Hi, thanks for reporting this. The reason why I reverted it is that I'm deferring the solution to I may need to revert and add the work around until the fix is applied in ggplot2 |
What is the suggested workaround for now, when the dataset is too big to be pulled into memory (and therefore cannot be coereced to numeric in R?)? Temporarily transform the type of the column in the database via some sql command maybe? |
Hi, you can use the corresponding |
@quartin / @henningsway - I reopened this issue because I just noticed that I may have inadvertently remove the temp fix I had to coerce automatically coerce the results. |
I think it would be really nice to be able to use the dbplot-plotting functions for int64-data, otherwise its less useful, if your database uses int64 types. I see, that handbuilding (computation, collect, coerce, plot) is an option, but it often takes four lines of code instead of one. (And I suppose the dbplot-commands are more for the quick-analysis and general concept of "doing things in the database" anyways?) |
The text was updated successfully, but these errors were encountered: