gh-138736: Fix sqlite3.Connection.blobopen *row* type and naming#138738
gh-138736: Fix sqlite3.Connection.blobopen *row* type and naming#138738erlend-aasland merged 10 commits intopython:mainfrom
sqlite3.Connection.blobopen *row* type and naming#138738Conversation
|
Err.... Actually... I'm very sorry but I think we should use the term "id". Here what I mean. The sqlite docs (https://sqlite.org/c3ref/blob_open.html) say ROWID (https://sqlite.org/lang_createtable.html#rowid). I think it's more precise than index because nothing guarantees that the first row has index 1 and there are tables without indices. More precisely, the sqlite3 docs say:
For instance in https://sqlite.org/queryplanner.html#_lookup_by_rowid, the rowId does not match the "index" if we were to consider the table as an array. So maybe ID is better (and the C code could be improved instead). |
|
Let's go with rowid, since that's what it is (according to the SQLite docs). |
|
We should also fix the docstring. And I'm inclined to also improve the parameter name (rename it from |
sqlite3.Connection.blobopen row typesqlite3.Connection.blobopen *row* type and naming
|
Thanks, @chirizxc! |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
|
GH-139062 is a backport of this pull request to the 3.14 branch. |
…er type and naming (python#138738) The 'row' parameter represents a ROWID. Clarify this in docs and docstrings. (cherry picked from commit 8eb1062)
|
GH-139063 is a backport of this pull request to the 3.13 branch. |
rowinsqlite3.Connection.blobopen#138736📚 Documentation preview 📚: https://cpython-previews--138738.org.readthedocs.build/