-
-
Notifications
You must be signed in to change notification settings - Fork 48
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
FAQ: why do I need to register methods for S3 generics from other modules/packages? #298
Comments
Context: Reddit discussion; to wit:
|
I wonder if this is related to this: ianmcook/implyr#57 |
I don’t think it’s related, since S3 classes in packages should just work with ‘box’. And the issue you’re linking to is related to S4 at any rate, not S3. S4 is another whole can of worms but you should be able to load and use packages that define S4 classes with ‘box’ without issues. Without being an S4 expert, it seems to me that the ’implyr’ package does some questionable things with regards to S4 registration which I believe will cause issues. In particular, it seems to explicitly register S4 classes in the global environment rather than in the package namespace. I don’t think packages are supposed to do that. I’d love to help diagnose that issue but I don’t have an Impala database handy, and setting up a mock database doesn’t seem trivial without preexisting knowledge. One thing you could try (to see whether this is related to ‘box’) is to perform a manual import of the relevant functions; that is, instead of using src_impala <- implyr::src_impala
dbGetQuery <- DBI::dbGetQuery
options(warn=1)
impala <- src_impala(drv = odbc::odbc(),
dsn = "my_dsn",
database = "default",
bigint = "character",
auto_disconnect = FALSE
)
ret <- dbGetQuery(impala, "show databases") If this also fails, the error is in ‘implyr’. |
No description provided.
The text was updated successfully, but these errors were encountered: