summaryrefslogtreecommitdiffstats
path: root/Modules/_sqlite/cursor.c
Commit message (Collapse)AuthorAgeFilesLines
* [2.7] prefix internal sqlite symbols with _pysqlite_ (GH-8215). (GH-8217)Benjamin Peterson2018-07-101-2/+2
| | | | | (cherry picked from commit 7762e4d3872818272800dfbd8e1d8e3a689eb8f2) Co-authored-by: Benjamin Peterson <benjamin@python.org>
* 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-071-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-141-1/+1
| | | This no-op change makes 2.7 more consistent with 3.x to ease comparison and backports.
* fix unused variable warnings in pysqlite (closes #27967)Benjamin Peterson2016-09-061-3/+1
|
* Issue #26200: Added Py_SETREF and replaced Py_XSETREF with Py_SETREFSerhiy Storchaka2016-04-101-3/+3
| | | | in places where Py_DECREF was used.
* Issue #22570: Renamed Py_SETREF to Py_XSETREF.Serhiy Storchaka2016-04-061-5/+5
|
* 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-241-8/+5
| | | | macro Py_SETREF.
* Issue #20437: Fixed 43 potential bugs when deleting objects references.Serhiy Storchaka2014-02-091-6/+3
|
* Issue #17857: Prevent build failures with pre-3.5.0 versions of sqlite3,Serhiy Storchaka2013-04-281-1/+1
| | | | | | | 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-071-17/+3
|
* Issue #10811: Fix recursive usage of cursors. Instead of crashing, raise a ↵Petri Lehtinen2012-02-061-10/+19
| | | | ProgrammingError now.
* sqlite3: Handle strings with embedded zeros correctlyPetri Lehtinen2012-02-011-7/+9
| | | | Closes #13676.
* Issue #13099: Fix sqlite3.Cursor.lastrowid under a Turkish locale.Antoine Pitrou2011-10-041-2/+2
| | | | Reported and diagnosed by Thomas Kluyver.
* Merged code from pysqlite 2.6.0.Gerhard Häring2010-03-051-20/+65
|
* Issue #3846: Release GIL during calls to sqlite3_prepare. This improves ↵Gerhard Häring2008-09-121-0/+2
| | | | 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-121-3/+3
| | | | 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.
* Issue #3153: sqlite leaks on error.Alexandre Vassalotti2008-07-131-5/+3
| | | | 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-15/+15
| | | | | | | 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-311-14/+10
| | | | DB-API 2.0 compliance.
* Renamed PyString to PyBytesChristian Heimes2008-05-261-15/+15
|
* 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.
* Update sqlite3 module to match current version of pysqlite.Gerhard Häring2008-03-281-1/+5
|
* Updated to pysqlite 2.4.1. Documentation additions will come later.Gerhard Häring2008-02-291-70/+79
|
* #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-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-104/+116
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-281-1/+1
|
* The sqlite3 module did cut off data from the SQLite database at the first nullGerhard Häring2006-07-021-2/+3
| | | | character before sending it to a custom converter. This has been fixed now.
* Merged changes from external pysqlite 2.3.0 release. Documentation updates willGerhard Häring2006-06-131-11/+40
| | | | follow in a few hours at the latest. Then we should be ready for beta1.
* 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-231-31/+27
|
* Fix problem (not checking return result) reported by CoverityNeal Norwitz2006-04-091-1/+4
|
* This change shouldn't have any functional effect. Coverity wasNeal Norwitz2006-04-061-1/+1
| | | | complaining because it seemed like parameters_iter could be NULL.
* upgrade to final version of pysqlite 2.2.0Anthony Baxter2006-04-051-1/+1
|
* Fix a couple of memory issuesNeal Norwitz2006-04-041-3/+3
|
* Update to pysqlite 2.2.0Anthony Baxter2006-04-041-16/+93
|
* Make ssize_t cleanNeal Norwitz2006-04-011-1/+1
|
* backport r243 from the pysqlite2 svn repository - lowers the required versionAnthony Baxter2006-04-011-124/+4
| | | | | | of SQLite3 from 3.2.2 to 3.0.8, by providing an alternative to sqlite3_transfer_bindings. setup.py also handles the common (in debian and ubuntu, at least) case of a buggy sqlite3.h SQLITE_VERSION_NUMBER.
* merged the sqlite-integration branch.Anthony Baxter2006-04-011-0/+1067
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-08-27 23:37:59 (GMT)