summaryrefslogtreecommitdiff
path: root/Modules/_sqlite
Commit message (Collapse)AuthorAgeFilesLines
* bpo-31764: Prevent a crash in sqlite3.Cursor.close() in case the Cursor ↵Oren Milman2017-11-081-0/+5
| | | | object is uninitialized (GH-4333)
* bpo-31770: Prevent a crash and refleaks when calling ↵Miss Islington (bot)2017-11-061-8/+7
| | | | | sqlite3.Cursor.__init__() more than once (GH-3968) (#4302) (cherry picked from commit e56ab746a965277ffcc4396d8a0902b6e072d049)
* consistently use Py_TYPE, Py_REFCNT, and correct initializer macros (#3563)Benjamin Peterson2017-09-132-2/+2
| | | This no-op change makes 2.7 more consistent with 3.x to ease comparison and backports.
* revert dd13098a5dc2 (#29006, #10513)Benjamin Peterson2017-01-161-1/+0
|
* revert 030e100f048a (#29006, #10513)Benjamin Peterson2017-01-111-0/+1
|
* fix refleak in null-containing error case (#21147)Benjamin Peterson2016-12-031-1/+2
|
* Issue #28480: Avoid label at end of compound statement --without-threadsMartin Panter2016-10-201-0/+1
|
* Issue #27897: Fixed possible crash in sqlite3.Connection.create_collation()Serhiy Storchaka2016-10-011-3/+5
| | | | if pass invalid string-like object as a name. Original patch by Xiang Zhang.
* fix unused variable warnings in pysqlite (closes #27967)Benjamin Peterson2016-09-062-6/+2
|
* Issue #27861: Fixed a crash in sqlite3.Connection.cursor() when a factorySerhiy Storchaka2016-08-291-2/+11
| | | | creates not a cursor. Patch by Xiang Zhang.
* Issue #10513: Fix a regression in Connection.commit()Berker Peksag2016-08-261-1/+0
| | | | | | Statements should not be reset after a commit. Backported from https://github.com/ghaering/pysqlite/commit/029050896b1e6058573abeef5a8970384c0c7faa
* English spelling and grammar fixesMartin Panter2016-07-112-2/+2
|
* Issue #26200: Added Py_SETREF and replaced Py_XSETREF with Py_SETREFSerhiy Storchaka2016-04-102-6/+6
| | | | in places where Py_DECREF was used.
* Issue #22570: Renamed Py_SETREF to Py_XSETREF.Serhiy Storchaka2016-04-062-9/+9
|
* Issue #20440: More use of Py_SETREF.Serhiy Storchaka2015-12-271-2/+2
| | | | | This patch is manually crafted and contains changes that couldn't be handled automatically.
* Issue #20440: Massive replacing unsafe attribute setting code with specialSerhiy Storchaka2015-12-242-16/+10
| | | | macro Py_SETREF.
* Issue #24257: Fixed segmentation fault in sqlite3.Row constructor with fakedSerhiy Storchaka2015-05-221-1/+1
| | | | cursor type.
* Issue #20274: When calling a _sqlite.Connection, it now complains if passedLarry Hastings2015-05-081-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 nullSerhiy Storchaka2014-09-112-3/+7
| | | | character instead of truncate it. Based on patch by Victor Stinner.
* Issue #21975: Fixed crash when using uninitialized sqlite3.Row (in particularSerhiy Storchaka2014-08-061-11/+17
| | | | | when unpickling pickled sqlite3.Row). sqlite3.Row is now initialized in the __new__() method.
* Issue #10203: sqlite3.Row now truly supports sequence protocol. In particularSerhiy Storchaka2014-05-281-2/+24
| | | | it supports reverse() and negative indices. Original patch by Claudiu Popa.
* Issue #20437: Fixed 43 potential bugs when deleting objects references.Serhiy Storchaka2014-02-092-8/+4
|
* Issue #20026: Fix the sqlite module to handle correctly invalid isolation levelVictor Stinner2013-12-191-1/+4
| | | | (wrong type).
* Issue #17857: Prevent build failures with pre-3.5.0 versions of sqlite3,Serhiy Storchaka2013-04-283-7/+7
| | | | | | | such as was shipped with Centos 5 and Mac OS X 10.4. This bug was already fixed in issue14572 for 2.7 only and then it was backported back from 3.3 in issue17073.
* Issue #17073: Fix some integer overflows in sqlite3 module.Serhiy Storchaka2013-02-075-63/+134
|
* Issue #14572: Prevent build failures with pre-3.5.0 versions ofNed Deily2012-05-191-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 architecturesPetri Lehtinen2012-02-211-5/+8
| | | | Closes #8033.
* Issue #10811: Fix recursive usage of cursors. Instead of crashing, raise a ↵Petri Lehtinen2012-02-062-10/+20
| | | | ProgrammingError now.
* sqlite3: Handle strings with embedded zeros correctlyPetri Lehtinen2012-02-012-11/+13
| | | | Closes #13676.
* Issue #13099: Fix sqlite3.Cursor.lastrowid under a Turkish locale.Antoine Pitrou2011-10-041-2/+2
| | | | Reported and diagnosed by Thomas Kluyver.
* #11565: Fix several typos. Patch by Piotr Kasprzyk.Ezio Melotti2011-03-161-1/+1
|
* Remove an unnecessary variable.Brett Cannon2010-05-051-3/+0
| | | | Found using Clang's static analyzer.
* sqlite3: Fix a segfault on calling a connection with something else than aVictor Stinner2010-03-131-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äring2010-03-0517-65/+323
|
* #5615: make it possible to configure --without-threads again.Georg Brandl2009-04-052-6/+32
|
* Issue #5341: Fix a variety of spelling errors.Mark Dickinson2009-02-211-1/+1
|
* Issue #3846: Release GIL during calls to sqlite3_prepare. This improves ↵Gerhard Häring2008-09-122-0/+6
| | | | concurrent access to the same database file from multiple threads/processes.
* Fixes issue #3103. In the sqlite3 module, made one more function static. All ↵Gerhard Häring2008-09-128-28/+28
| | | | 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äring2008-09-121-1/+1
| | | | methods not found in DB-API.
* Silenced a compiler warning in the sqlite moduleChristian Heimes2008-08-221-2/+2
| | | | | Modules/_sqlite/row.c:187: warning: suggest parentheses around && within || Reviewed by Benjamin Peterson
* #3312: fix two sqlite3 crashes.Georg Brandl2008-07-162-3/+13
|
* Issue #3153: sqlite leaks on error.Alexandre Vassalotti2008-07-132-23/+12
| | | | Changed statements of the form Py_DECREF(obj), obj = 0 to Py_CLEAR(obj).
* Expand docstrings of sqlite3 functions.Georg Brandl2008-06-221-12/+52
|
* This reverts r63675 based on the discussion in this thread:Gregory P. Smith2008-06-097-50/+50
| | | | | | | 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.
* Fixed rowcount for SELECT statements. They're -1 now (again), for better ↵Gerhard Häring2008-05-312-15/+11
| | | | DB-API 2.0 compliance.
* Renamed PyString to PyBytesChristian Heimes2008-05-267-50/+50
|
* Implemented feature request 2157: Converter names are cut off at '('Gerhard Häring2008-05-041-1/+5
| | | | | | characters. This avoids the common case of something like 'NUMBER(10)' not being parsed as 'NUMBER', like expected. Also corrected the docs about converter names being case-sensitive. They aren't any longer.
* Applied sqliterow-richcmp.diff patch from Thomas Heller in Issue2152. TheGerhard Häring2008-05-041-2/+26
| | | | sqlite3.Row type is now correctly hashable.
* SQLite requires 64-bit integers in order to build. So the whole HAVE_LONG_LONGGerhard Häring2008-05-041-4/+0
| | | | #ifdefing was useless.
* Update sqlite3 module to match current version of pysqlite.Gerhard Häring2008-03-288-15/+35
|