-
Notifications
You must be signed in to change notification settings - Fork 40
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
Error in result_fetch(res@ptr, n = n) : Error fetching buffer: #135
Comments
I have the same problem, also with R 3.6.0 on Mojave. Installing RMariaDB from source did not help. Anything that tries to fetch results fails (I've tried |
We had the same problem too. I could make it work on ubuntu (with a recent install of I tried installing from source and got a warning My workaround was to install up to date versions of
The second link forces the brew version to be the default - importantly it forces the C compiler to link to the brew libraries. Then in R I installed from source
And it worked. Hope that helps! |
Thanks a lot! That workaround also worked for me. |
This almost worked for me, but
|
Thanks. So, installing MySQL client drivers is the only solution on macOS? Did anyone succeed with the MariaDB connector? |
I tried |
Can second this. Tried both of these before the workaround mentioned above. |
In case there are more MacPorts users with this problem: I got it to work by installing the |
same problem here Mac OS Mojave. Solved with mentioned brew workaround. Installing MariaDB connector did not work |
fwiw, I also ran into this error when upgrading to R 3.6.0 (with MariaDB 10.3.11). The workaround above didn't work for me, but upgrading to MariaDB 10.4.6 and reinstalling RMariaDB from source fixed it. |
I had the same issue in macOS Mojave and in the end it worked, but after
I needed an additional step to be able to re-install RMariaDb in RStudio without the following Error: ld: warning: directory not found for option '-L/usr/local/opt/openssl/lib' This worked for me before re-installing RMariaDb:
[https://blog.twobucks.co/ld-warning-directory-not-found-for-option/] |
An update
may no longer work (depending no your system configuration, you may get a load of C++ compiler errors), but
just worked for me this time |
@jeroen: Any idea how to fix the binary build for the Mac? Do you know (or know how to find out) what libraries CRAN is using, so that we can replicate locally? |
Right now we build against
Maybe we should improve |
What is the easiest way for me to reproduce this problem on macos? Does it happen when running a local postgres server ? |
I think a local MySQL or MariaDB server is enough to reproduce the problem. I'll look into giving better output with |
But why doesn't it fail on travis then? |
I think this issue is about failures with installations of packages pre-built by CRAN? |
We simulate CRAN on Travis with the build that has |
I believe this problem has been solved by updating mariadb-connector-c that we use to build the CRAN binaries from 3.0.8 to 3.1.6. I can no longer reproduce this problem locally. But you need to resubmit to CRAN to trigger a new build of the R binary package. |
Thanks, will do! |
I'll also submit a new version of RMySQL, just to be sure. Although it seems like this may have been a bug in mariadb-connector-c 3.0.5 in a part of the code that is not used by RMySQL. |
FYI, the new version RMySQL 0.10.18 on cran is now built with mariadb-connector-c to 3.1.6. |
Closing for now, please open a new issue if problems persist. |
This old thread has been automatically locked. If you think you have found something related to this, please open a new issue and link to this old issue if necessary. |
Just updated R to version 3.6.0 and was looking through some old projects to make sure everything still ran smoothly. I have a Shiny app which accesses a local server, but now the server will not connect and throws the error in the title when trying to access specific tables in the database.
I saw this issue in some older reports, but I never came across it until just today when I updated R. So I thought I would report the issue just in case it has anything to do with that.
The text was updated successfully, but these errors were encountered: