You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Empty bytestrings are not longer returned on SQLite. #87534
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee=Noneclosed_at=<Date2021-03-03.14:16:41.453>created_at=<Date2021-03-02.11:52:08.762>labels= ['type-bug', 'library', '3.10']
title='Empty bytestrings are not longer returned on SQLite.'updated_at=<Date2021-03-03.14:16:41.452>user='https://github.com/felixxm'
We noticed a regression in Python3.10.0a6 (it works properly in Python3.10.0a5) when running Django's test suite. Empty bytestrings are not longer returned properly on SQLite:
Activity
felixxm commentedon Mar 2, 2021
We noticed a regression in Python3.10.0a6 (it works properly in Python3.10.0a5) when running Django's test suite. Empty bytestrings are not longer returned properly on SQLite:
Regression in 47feb1f
See https://bugs.python.org/issue43249
I will submit PR in few minutes.
erlend-aasland commentedon Mar 2, 2021
sqlite3_column_blob() should be handled like sqlite3_value_blob() in #68862:
In case of NULL, check sqlite3_errcode() and raise MemoryError if needed. Else it's a zero-sized blob.
erlend-aasland commentedon Mar 2, 2021
I created bpo-43369 for out-of-memory error handling, since it also applies to sqlite3_column_text().
berkerpeksag commentedon Mar 3, 2021
New changeset 3b4b2cf by Mariusz Felisiak in branch 'master':
bpo-43368: Fix fetching empty bytes in sqlite3 (GH-24706)
3b4b2cf