summaryrefslogtreecommitdiffstats
path: root/Modules/_sqlite/connection.c
Commit message (Collapse)AuthorAgeFilesLines
* #5615: make it possible to configure --without-threads again.Georg Brandl2009-04-051-6/+30
|
* Issue #5341: Fix a variety of spelling errors.Mark Dickinson2009-02-211-1/+1
|
* Fixes issue #3103. In the sqlite3 module, made one more function static. All ↵Gerhard Häring2008-09-121-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äring2008-09-121-1/+1
| | | | methods not found in DB-API.
* #3312: fix two sqlite3 crashes.Georg Brandl2008-07-161-2/+9
|
* Issue #3153: sqlite leaks on error.Alexandre Vassalotti2008-07-131-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. Smith2008-06-091-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 PyBytesChristian Heimes2008-05-261-17/+17
|
* 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-291-34/+197
|
* #1629: Renamed Py_Size, Py_Type and Py_Refcnt to Py_SIZE, Py_TYPE and ↵Christian Heimes2007-12-191-1/+1
| | | | Py_REFCNT. Macros for b/w compatibility are available.
* PEP 3123: Provide forward compatibility with Python 3.0, while keepingMartin v. Löwis2007-07-211-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 beGerhard Häring2007-01-141-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 weakGerhard Häring2006-06-191-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 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-131-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äring2006-04-231-67/+130
|
* Fix memory leakNeal Norwitz2006-04-161-1/+5
|
* Fix unchecked return result from Coverity.Neal Norwitz2006-04-061-0/+2
|
* upgrade to final version of pysqlite 2.2.0Anthony Baxter2006-04-051-1/+1
|
* Update to pysqlite 2.2.0Anthony Baxter2006-04-041-1/+155
|
* Make ssize_t cleanNeal Norwitz2006-04-011-2/+2
|
* merged the sqlite-integration branch.Anthony Baxter2006-04-011-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.
generated by cgit v0.12 at 2025-09-16 06:01:56 (GMT)