Add LOB support - #139
Open
Vnajeb wants to merge 6 commits into
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
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.
Resolves #88
Changes proposed in this pull request:
lob.pythat expose a PEP 249-style read() method, matching DB-API 2.0.row_to_tupleinspects each column's SQL type and wraps LOB values on the way out, so callers get ClobValue/BlobValue instances without any extra opt-in.cursor.execute(sql, isTerseResults=True)used to return raw CLOB/BLOB values in list rows since the old code only handled dicts it now wraps list rows the same way, so both row shapes behave consistently.tests/unit/test_lob.pycovers ClobValue/BlobValue construction,read()chunking/exhaustion, and NULL handling, while tests/unit/test_cursor_pep249.py adds end-to-end coverage throughCursor.execute/fetchone/fetchall, including the terse-mode regression case.