[issue24887] Sqlite3 has no option to provide open flags

Changes by Berker Peksag : -- resolution: -> out of date stage: patch review -> resolved status: open -> closed ___ Python tracker ___ __

[issue24887] Sqlite3 has no option to provide open flags

Aviv Palivoda added the comment: IMO this issue can be closed as the URI filename interface can be used instead of the flags. The URI interface parameters can override the flags given as specified in: https://www.sqlite.org/c3ref/open.html -- nosy: +palaviv ___

[issue24887] Sqlite3 has no option to provide open flags

Berker Peksag added the comment: URI filename support has been added in f13bb1e40fbc (Python 3.4+). db = sqlite3.connect('file:path/to/database?mode=ro', uri=True) Here is a patch that adds a new flags parameter to sqlite3.connect(). -- dependencies: -Migrate sqlite3 module to _v2

[issue24887] Sqlite3 has no option to provide open flags

Changes by Berker Peksag : -- dependencies: +Migrate sqlite3 module to _v2 API to enhance performance stage: -> needs patch type: -> enhancement ___ Python tracker ___

[issue24887] Sqlite3 has no option to provide open flags

Gerhard Häring added the comment: It requires switch to the v2 open function of the SQLite C API. While we're at it, we can also enable URI filenames. -- assignee: -> ghaering nosy: +ghaering versions: +Python 3.6 -Python 3.4 ___ Python tracker

[issue24887] Sqlite3 has no option to provide open flags

New submission from Cal Leeming: There are several flags which can be provided to Sqlite3 during connection [1]. Alternative libraries such as apsw provide the ability to use these flags [2], however it would be nice if `sqlite3` supported this out of the box. Is there any reason why the wrapp