-
Notifications
You must be signed in to change notification settings - Fork 111
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
Lack of BLOB support #123
Comments
Thanks. This looks like a known issue (#49), we will report there as soon as there is progress on that front. |
gtmaskall - could you share your workaround in more detail? I'm facing the same issue and I'm trying to find a workaround to this. |
Hi @ElianoMarques , Extract the BLOB by getting the server to convert the data to a HEX string, like Hope this helps, |
Thanks. I wrote another way that just works nicely. If you store the object as text with the following:
Then store the object as text into Mysql. then use the following:
Hope this also works for you. |
Thanks for the suggestion, but I don't have control of the stored data; I have to work with it "as is". |
Closing as duplicate. |
dbGetQuery(conn, "SELECT a FROM table") where a is a BLOB results in message about truncated field (and no data). Equivalent operation using RSQLite results in correct raw vector being returned, which can then be read as binary. My workaround with RMySQL is to request the server to cast the field to a HEX string, which you can then parse into a RAW and then read as binary. It would be great to have the same functionality for BLOBs in RMySQL as in SQLite.
The text was updated successfully, but these errors were encountered: