AJDA-214: Update ODBC driver #44
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…es fetch() method - mainly to set the odbc_longreadlen property
MiroCillik
commented
Jun 2, 2025
Comment on lines
+30
to
+32
| $parameters['DefaultStringColumnLength'] = '16777216'; | ||
| $parameters['DefaultVarcharColumnLength'] = '16777216'; | ||
| $parameters['BinaryColumnLength'] = '16777216'; |
There was a problem hiding this comment.
Timhle si nejsem jistej, jestli to ma opravdu vlyv, ale funguje to takhle, uz to tak necham.
Kdyby se objevil problem, tak to muzem postelovat
|
Tady je videt, ze to funguje, puvodni konfigurace i s procesorama a PKs (verze 14): A ze i data jsou cela, neni tam zadny null, nebo nekompletni XML: A jeste potrebuji skusit verzi 15, kde jsou upravy OdbcQueryResult presunuty z db-extractor-adapter sem do tridy HiveOdbcQueryResult |
|
Vali to i s verzi "15": 
|
ondrajodas
reviewed
Jun 3, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
https://keboola.atlassian.net/browse/AJDA-214
Story
The extractor was failing on segmentation fault --> updated driver (use Debian one, not RPM)
The new driver was throwing exception on getting primary keys --> needed to update db-extractor-adapter keboola/db-extractor-adapter#35
The I was experimenting with settings for odbc_longreadlen, suggested by AI, which helped when I put large enough number there :)
The last problem was corrupted utf-8 character, so I put utf8 sanitization into the extractor itself.
Changes