-
Notifications
You must be signed in to change notification settings - Fork 62
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 converting ODBC.Cursor to DataFrame #306
Comments
@ElOceanografo , sorry for the delay here; could you share which database you're connected to here? What version? Are you running on linux/osx/windows? I'd like to try and reproduce the error you're seeing to figure out what's going on. |
Attempt at fixing #306. It's a little unclear what's going on here; for some reason, our length indicator is coming back with a value of 12, even though the column size told us it wouldn't be more than 11 bytes. I think we're correctly incrementing the columnsize of Dec64 by 1 because the C storage is SQL_C_CHAR, but yeah, I don't understand why it's coming back w/ more bytes that we're expecting. My main worry with this fix is if we're actually missing a byte that should be included in the final Dec64 number, but this should at least allow us to materialize the full result.
@ElOceanografo , could you try the fix I have in #308 to see if it fixes your issue? I'm a little worried that the solution in that PR is missing out on a byte that the result should have for the |
Sorry for the slow response. I'm not sure what happened, but after updating Julia from 1.4 to 1.5 and updating ODBC to v1.0.3, I am no longer getting this error. I'll try out a few more queries on different databases and close the issue if it doesn't crop up again. |
Just faced similar problem on MS SQL Server, ODBC v1.0.4, julia 1.5: iteration through Table rows failed with similar BoundsError on Line 355 in d603519
Branch Would try to isolate data later this week. |
@caligo-mentis , if you run into issues on the current release, please open a new issue. I'm going to close this one as I think the original issue is resolved. |
I'm attempting to update some of my code to the ODBC 1.0 interface, and it no longer works. Specifically, when I try to convert the results of a query to a
DataFrame
, I get this error:The same query worked in the pre-1.0 interface (i.e. using
ODBC.query(connection, sql_query)
), and when I copy-paste thesql_query
as a string into Oracle SQL Developer it returns the expected table, so that isn't the issue. Other queries to other tables in the same database also run and convert toDataFrame
without problems.In case it helps, this is what the result of the
execute
call looks like:The text was updated successfully, but these errors were encountered: