Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | consistently use Py_TYPE, Py_REFCNT, and correct initializer macros (#3563) | Benjamin Peterson | 2017-09-14 | 1 | -1/+1 |
| | | | This no-op change makes 2.7 more consistent with 3.x to ease comparison and backports. | ||||
* | revert dd13098a5dc2 (#29006, #10513) | Benjamin Peterson | 2017-01-16 | 1 | -1/+0 |
| | |||||
* | revert 030e100f048a (#29006, #10513) | Benjamin Peterson | 2017-01-12 | 1 | -0/+1 |
| | |||||
* | Issue #28480: Avoid label at end of compound statement --without-threads | Martin Panter | 2016-10-20 | 1 | -0/+1 |
| | |||||
* | Issue #27897: Fixed possible crash in sqlite3.Connection.create_collation() | Serhiy Storchaka | 2016-10-01 | 1 | -3/+5 |
| | | | | if pass invalid string-like object as a name. Original patch by Xiang Zhang. | ||||
* | Issue #27861: Fixed a crash in sqlite3.Connection.cursor() when a factory | Serhiy Storchaka | 2016-08-29 | 1 | -2/+11 |
| | | | | creates not a cursor. Patch by Xiang Zhang. | ||||
* | Issue #10513: Fix a regression in Connection.commit() | Berker Peksag | 2016-08-26 | 1 | -1/+0 |
| | | | | | | Statements should not be reset after a commit. Backported from https://github.com/ghaering/pysqlite/commit/029050896b1e6058573abeef5a8970384c0c7faa | ||||
* | English spelling and grammar fixes | Martin Panter | 2016-07-11 | 1 | -1/+1 |
| | |||||
* | Issue #26200: Added Py_SETREF and replaced Py_XSETREF with Py_SETREF | Serhiy Storchaka | 2016-04-10 | 1 | -3/+3 |
| | | | | in places where Py_DECREF was used. | ||||
* | Issue #22570: Renamed Py_SETREF to Py_XSETREF. | Serhiy Storchaka | 2016-04-06 | 1 | -4/+4 |
| | |||||
* | Issue #20440: Massive replacing unsafe attribute setting code with special | Serhiy Storchaka | 2015-12-24 | 1 | -8/+5 |
| | | | | macro Py_SETREF. | ||||
* | Issue #20274: When calling a _sqlite.Connection, it now complains if passed | Larry Hastings | 2015-05-08 | 1 | -3/+6 |
| | | | | | | any keyword arguments. Previously it silently ignored them. Also: Remove ignored and erroneous "kwargs" parameters from three METH_VARARGS methods on _sqlite.Connection. | ||||
* | Issue #21147: sqlite3 now raises an exception if the request contains a null | Serhiy Storchaka | 2014-09-11 | 1 | -1/+2 |
| | | | | character instead of truncate it. Based on patch by Victor Stinner. | ||||
* | Issue #20437: Fixed 43 potential bugs when deleting objects references. | Serhiy Storchaka | 2014-02-09 | 1 | -2/+1 |
| | |||||
* | Issue #20026: Fix the sqlite module to handle correctly invalid isolation level | Victor Stinner | 2013-12-19 | 1 | -1/+4 |
| | | | | (wrong type). | ||||
* | Issue #17073: Fix some integer overflows in sqlite3 module. | Serhiy Storchaka | 2013-02-07 | 1 | -36/+48 |
| | |||||
* | Issue #14572: Prevent build failures with pre-3.5.0 versions of | Ned Deily | 2012-05-20 | 1 | -2/+2 |
| | | | | sqlite3, such as was shipped with Centos 5 and Mac OS X 10.4. | ||||
* | sqlite3: Fix 64-bit integer handling in user functions on 32-bit architectures | Petri Lehtinen | 2012-02-21 | 1 | -5/+8 |
| | | | | Closes #8033. | ||||
* | Remove an unnecessary variable. | Brett Cannon | 2010-05-05 | 1 | -3/+0 |
| | | | | Found using Clang's static analyzer. | ||||
* | sqlite3: Fix a segfault on calling a connection with something else than a | Victor Stinner | 2010-03-13 | 1 | -0/+6 |
| | | | | | | | | string. Initialize all attributes to be able to call the statement destructor on error. Avoid also a duplicate connection in some tests: setUp() does already open a connection (":memory:"). | ||||
* | Merged code from pysqlite 2.6.0. | Gerhard Häring | 2010-03-05 | 1 | -16/+190 |
| | |||||
* | #5615: make it possible to configure --without-threads again. | Georg Brandl | 2009-04-05 | 1 | -6/+30 |
| | |||||
* | Issue #5341: Fix a variety of spelling errors. | Mark Dickinson | 2009-02-21 | 1 | -1/+1 |
| | |||||
* | Fixes issue #3103. In the sqlite3 module, made one more function static. All ↵ | Gerhard Häring | 2008-09-12 | 1 | -4/+4 |
| | | | | renaming public symbos now have the pysqlite prefix to avoid name clashes. This at least once created problems where the same symbol name appeared somewhere in Apache and the sqlite3 module was used from mod_python. | ||||
* | sqlite3 module: Mark iterdump() method as "Non-standard" like all the other ↵ | Gerhard Häring | 2008-09-12 | 1 | -1/+1 |
| | | | | methods not found in DB-API. | ||||
* | #3312: fix two sqlite3 crashes. | Georg Brandl | 2008-07-16 | 1 | -2/+9 |
| | |||||
* | Issue #3153: sqlite leaks on error. | Alexandre Vassalotti | 2008-07-13 | 1 | -18/+9 |
| | | | | Changed statements of the form Py_DECREF(obj), obj = 0 to Py_CLEAR(obj). | ||||
* | This reverts r63675 based on the discussion in this thread: | Gregory P. Smith | 2008-06-09 | 1 | -17/+17 |
| | | | | | | | http://mail.python.org/pipermail/python-dev/2008-June/079988.html Python 2.6 should stick with PyString_* in its codebase. The PyBytes_* names in the spirit of 3.0 are available via a #define only. See the email thread. | ||||
* | Renamed PyString to PyBytes | Christian Heimes | 2008-05-26 | 1 | -17/+17 |
| | |||||
* | Accept patch issue2426 by Paul Kippes (kippesp). | Gregory P. Smith | 2008-03-28 | 1 | -0/+48 |
| | | | | Adds sqlite3.Connection.iterdump to allow dumping of databases. | ||||
* | Only DECREF if ret != NULL | Neal Norwitz | 2008-03-03 | 1 | -1/+1 |
| | |||||
* | Updated to pysqlite 2.4.1. Documentation additions will come later. | Gerhard Häring | 2008-02-29 | 1 | -34/+197 |
| | |||||
* | #1629: Renamed Py_Size, Py_Type and Py_Refcnt to Py_SIZE, Py_TYPE and ↵ | Christian Heimes | 2007-12-19 | 1 | -1/+1 |
| | | | | Py_REFCNT. Macros for b/w compatibility are available. | ||||
* | PEP 3123: Provide forward compatibility with Python 3.0, while keeping | Martin v. Löwis | 2007-07-21 | 1 | -3/+2 |
| | | | | | backwards compatibility. Add Py_Refcnt, Py_Type, Py_Size, and PyVarObject_HEAD_INIT. | ||||
* | Merged changes from standalone version 2.3.3. This should probably all be | Gerhard Häring | 2007-01-14 | 1 | -130/+130 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | merged into the 2.5 maintenance branch: - self->statement was not checked while fetching data, which could lead to crashes if you used the pysqlite API in unusual ways. Closing the cursor and continuing to fetch data was enough. - Converters are stored in a converters dictionary. The converter name is uppercased first. The old upper-casing algorithm was wrong and was replaced by a simple call to the Python string's upper() method instead. -Applied patch by Glyph Lefkowitz that fixes the problem with subsequent SQLITE_SCHEMA errors. - Improvement to the row type: rows can now be iterated over and have a keys() method. This improves compatibility with both tuple and dict a lot. - A bugfix for the subsecond resolution in timestamps. - Corrected the way the flags PARSE_DECLTYPES and PARSE_COLNAMES are checked for. Now they work as documented. - gcc on Linux sucks. It exports all symbols by default in shared libraries, so if symbols are not unique it can lead to problems with symbol lookup. pysqlite used to crash under Apache when mod_cache was enabled because both modules had the symbol cache_init. I fixed this by applying the prefix pysqlite_ almost everywhere. Sigh. | ||||
* | Fixed a memory leak that was introduced with incorrect usage of the Python weak | Gerhard Häring | 2006-06-19 | 1 | -1/+1 |
| | | | | | | reference API in pysqlite 2.2.1. Bumbed pysqlite version number to upcoming pysqlite 2.3.1 release. | ||||
* | Speculative checkin (requires approval of Gerhard Haering) | Neal Norwitz | 2006-06-15 | 1 | -0/+2 |
| | | | | | | | | | This backs out the test changes in 46962 which prevented crashes by not running the tests via a version check. All the version checks added in that rev were removed from the tests. Code was added to the error handler in connection.c that seems to work with older versions of sqlite including 3.1.3. | ||||
* | - Added version checks in C code to make sure we don't trigger bugs in older | Gerhard Häring | 2006-06-14 | 1 | -4/+15 |
| | | | | | | | | | | | SQLite versions. - Added version checks in test suite so that we don't execute tests that we know will fail with older (buggy) SQLite versions. Now, all tests should run against all SQLite versions from 3.0.8 until 3.3.6 (latest one now). The sqlite3 module can be built against all these SQLite versions and the sqlite3 module does its best to not trigger bugs in SQLite, but using SQLite 3.3.3 or later is recommended. | ||||
* | Merged changes from external pysqlite 2.3.0 release. Documentation updates will | Gerhard Häring | 2006-06-13 | 1 | -11/+108 |
| | | | | follow in a few hours at the latest. Then we should be ready for beta1. | ||||
* | Updated the sqlite3 module to the external pysqlite 2.2.2 version. | Gerhard Häring | 2006-04-23 | 1 | -67/+130 |
| | |||||
* | Fix memory leak | Neal Norwitz | 2006-04-16 | 1 | -1/+5 |
| | |||||
* | Fix unchecked return result from Coverity. | Neal Norwitz | 2006-04-06 | 1 | -0/+2 |
| | |||||
* | upgrade to final version of pysqlite 2.2.0 | Anthony Baxter | 2006-04-05 | 1 | -1/+1 |
| | |||||
* | Update to pysqlite 2.2.0 | Anthony Baxter | 2006-04-04 | 1 | -1/+155 |
| | |||||
* | Make ssize_t clean | Neal Norwitz | 2006-04-01 | 1 | -2/+2 |
| | |||||
* | merged the sqlite-integration branch. | Anthony Baxter | 2006-04-01 | 1 | -0/+922 |
This is based on pysqlite2.1.3, and provides a DB-API interface in the standard library. You'll need sqlite 3.2.2 or later to build this - if you have an earlier version, the C extension module will not be built. |