-
-
Notifications
You must be signed in to change notification settings - Fork 32.1k
bpo-44822: Don't truncate str
s with embedded NULL chars returned by sqlite3
UDF callbacks
#27588
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
Changes from 6 commits
2241795
58d3244
73639f1
60d94f9
10fbc4b
a483052
55963ca
7a2c279
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
@@ -0,0 +1,3 @@ | ||||||
:mod:`sqlite3` now raises :exc:`OverflowError` if an user-defined function | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Actually sqlite3 overwrites OverflowError with other exception. But it does not matter, the most important part of this PR is that result strings with NUL are now correctly supported. Something like (please correct my English):
Suggested change
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Ah, yes, there should be some exception chaining in the UDF callbacks. I'll open an issue for it. Anyway, how does the reworded NEWS entry look?
erlend-aasland marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||
returns a :class:`str` larger than ``INT_MAX`` bytes. Patch by Erlend E. | ||||||
Aasland. |
Uh oh!
There was an error while loading. Please reload this page.