Message283363
| Author |
gumblex |
| Recipients |
gumblex |
| Date |
2016年12月16日.03:24:51 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1481858693.19.0.888054078986.issue28985@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
We have the sqlite3.set_authorizer function, where the first argument to its callback is one of the Authorizer Action Codes that the SQLite documentations defines[1]. However, the constants in the sqlite3 module is not up to date. The code in _sqlite/module.c haven't been updated since June, 2006.
According to the SQLite Changelog[2] and digging through the history,
* 2006年08月12日 (3.3.7) added SQLITE_CREATE_VTABLE, SQLITE_DROP_VTABLE
* 2006年10月09日 (3.3.8) added SQLITE_FUNCTION
* 2009年01月12日 (3.6.8) added SQLITE_SAVEPOINT
* 2014年02月03日 (3.8.3) added SQLITE_RECURSIVE
The constants above should be present in the module. The documentation[3] says, "All necessary constants are available in the sqlite3 module."
[1] https://sqlite.org/c3ref/c_alter_table.html
[2] https://sqlite.org/changes.html
[3] https://docs.python.org/3/library/sqlite3.html#sqlite3.Connection.set_authorizer |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2016年12月16日 03:24:53 | gumblex | set | recipients:
+ gumblex |
| 2016年12月16日 03:24:53 | gumblex | set | messageid: <1481858693.19.0.888054078986.issue28985@psf.upfronthosting.co.za> |
| 2016年12月16日 03:24:52 | gumblex | link | issue28985 messages |
| 2016年12月16日 03:24:52 | gumblex | create |
|