summaryrefslogtreecommitdiffstats
path: root/Modules/_sqlite
Commit message (Collapse)AuthorAgeFilesLines
* 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-201-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
|
* Accept patch issue2426 by Paul Kippes (kippesp).Gregory P. Smith2008-03-281-0/+48
| | | | Adds sqlite3.Connection.iterdump to allow dumping of databases.
* Only DECREF if ret != NULLNeal Norwitz2008-03-031-1/+1
|
* Updated to pysqlite 2.4.1. Documentation additions will come later.Gerhard Häring2008-02-2910-202/+483
|
* #1509: fix sqlite3 docstrings and docs w.r.t. cursor.fetchXXX methods.Georg Brandl2008-01-191-3/+3
|
* #1629: Renamed Py_Size, Py_Type and Py_Refcnt to Py_SIZE, Py_TYPE and ↵Christian Heimes2007-12-196-8/+8
| | | | Py_REFCNT. Macros for b/w compatibility are available.
* Forward-port of commit 59184.Gerhard Häring2007-12-112-4/+14
| | | | | | | | | - Backported a workaround for a bug in SQLite 3.2.x/3.3.x versions where a statement recompilation with no bound parameters lead to a segfault - Backported a fix necessary because of an SQLite API change in version 3.5. This prevents segfaults when executing empty queries, like our test suite does
* PEP 3123: Provide forward compatibility with Python 3.0, while keepingMartin v. Löwis2007-07-216-22/+15
| | | | | backwards compatibility. Add Py_Refcnt, Py_Type, Py_Size, and PyVarObject_HEAD_INIT.
* Patch by Tim Delany (missing DECREF). SF #1731330.Guido van Rossum2007-06-051-0/+1
|
* Merged changes from standalone version 2.3.3. This should probably all beGerhard Häring2007-01-1418-484/+518
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* Fix spelling.Georg Brandl2006-07-283-3/+3
|
* The sqlite3 module did cut off data from the SQLite database at the first nullGerhard Häring2006-07-022-3/+4
| | | | character before sending it to a custom converter. This has been fixed now.
* Fixed a memory leak that was introduced with incorrect usage of the Python weakGerhard Häring2006-06-192-2/+2
| | | | | | 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 Norwitz2006-06-151-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 olderGerhard Häring2006-06-141-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 willGerhard Häring2006-06-134-58/+266
| | | | follow in a few hours at the latest. Then we should be ready for beta1.
* More memory leaks from valgrindNeal Norwitz2006-06-021-0/+4
|
* Fix some warnings on Mac OS X 10.4Neal Norwitz2006-04-281-0/+4
|
* Updated the sqlite3 module to the external pysqlite 2.2.2 version.Gerhard Häring2006-04-2315-262/+229
|
* Fix valgrind problem with invalid memory readNeal Norwitz2006-04-161-2/+1
|
* Fix memory leakNeal Norwitz2006-04-161-1/+5
|
* Fix problem (not checking return result) reported by CoverityNeal Norwitz2006-04-091-1/+4
|
generated by cgit v0.12 at 2025-12-30 05:33:52 (GMT)