summaryrefslogtreecommitdiffstats
path: root/Lib/sqlite3/test
Commit message (Collapse)AuthorAgeFilesLines
* Issue #21147: sqlite3 now raises an exception if the request contains a nullSerhiy Storchaka2014-09-111-0/+10
| | | | character instead of truncate it. Based on patch by Victor Stinner.
* Issue #22340: Fix Python 3 warnings in Python 2 testsVictor Stinner2014-09-053-11/+23
|
* Issue #10203: sqlite3.Row now truly supports sequence protocol. In particularSerhiy Storchaka2014-05-281-3/+31
| | | | it supports reverse() and negative indices. Original patch by Claudiu Popa.
* weaken callback count inequality (closes #20901)Benjamin Peterson2014-03-131-1/+1
|
* add missing test assertion (closes #20080)Benjamin Peterson2014-02-151-0/+1
| | | | Patch by Vajrasky Kok.
* Issue #20026: Fix the sqlite module to handle correctly invalid isolation levelVictor Stinner2013-12-191-0/+5
| | | | (wrong type).
* Issue #19601: Use specific asserts in sqlite3 tests.Serhiy Storchaka2013-11-162-30/+20
|
* #18741: fix more typos. Patch by Févry Thibault.Ezio Melotti2013-08-172-3/+5
|
* Issue #14720: Enhance sqlite3 microsecond conversion, document its behaviorPetri Lehtinen2013-02-261-2/+11
|
* Issue #14720: sqlite3: Convert datetime microseconds correctlyPetri Lehtinen2013-02-231-1/+18
| | | | Patch by Lowe Thiderman
* Issue #17073: Fix some integer overflows in sqlite3 module.Serhiy Storchaka2013-02-072-12/+67
|
* #15109: revert '%'->'format' changes in 4b105d328fe7 to fix regression.R David Murray2013-01-111-0/+2
| | | | | | | With '%', non-ascii worked because the '%' automatically got promoted to unicode. With format that doesn't happen, which led to encoding errors. This fix goes back to using %, and adds a test to make sure non-ascii string values work in iterdump.
* #15545: sort iterdump via SQL instead of in python codeR David Murray2013-01-101-0/+21
| | | | | | | | | | | | Although there is not a regression in Python2, we make the same update here to keep the code bases in sync. (The fix for issue 9750 introduced a regression in Python 3 by sorting the row objects returned by fetchall. But if a row_factory such as sqlite3.Row is used, the rows may not be sortable (in Python3), which leads to an exception. The sorting is still a nice idea, so the patch moves the sort into the sql.) Fix and test by Peter Otten.
* sqlite3: Fix 64-bit integer handling in user functions on 32-bit architecturesPetri Lehtinen2012-02-211-0/+18
| | | | Closes #8033.
* Fix a variable scoping error in an sqlite3 testPetri Lehtinen2012-02-171-3/+3
| | | | | | Initial patch by Torsten Landschoff. Closes #11689.
* Fix sqlite3.Connection.iterdump on tables/fields with reserved names or quotesPetri Lehtinen2012-02-121-0/+8
| | | | Closes #9750
* Issue #10811: Fix recursive usage of cursors. Instead of crashing, raise a ↵Petri Lehtinen2012-02-061-0/+22
| | | | ProgrammingError now.
* sqlite3: Handle strings with embedded zeros correctlyPetri Lehtinen2012-02-012-1/+47
| | | | Closes #13676.
* Merged revisions 86596 via svnmerge fromEzio Melotti2010-11-212-3/+3
| | | | | | | | | | svn+ssh://pythondev@svn.python.org/python/branches/py3k ........ r86596 | ezio.melotti | 2010-11-20 21:04:17 +0200 (Sat, 20 Nov 2010) | 1 line #9424: Replace deprecated assert* methods in the Python test suite. ........
* Issue #7449, last part (11): fix many tests if thread support is disabledVictor Stinner2010-04-271-1/+5
| | | | | | * Use try/except ImportError or test_support.import_module() to import thread and threading modules * Add @unittest.skipUnless(threading, ...) to testcases using threads
* sqlite3: Fix a segfault on calling a connection with something else than aVictor Stinner2010-03-131-7/+12
| | | | | | | | 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-054-17/+252
|
* #7092: Silence more py3k warnings. Patch by Florent Xicluna.Ezio Melotti2010-02-032-5/+5
|
* #6026 - fix tests that failed without zlibEzio Melotti2009-09-121-1/+7
|
* Merge r73838 from py3k branch. Use the nondeprecated unittest methodGregory P. Smith2009-07-048-155/+155
| | | | names.
* #3312: fix two sqlite3 crashes.Georg Brandl2008-07-161-0/+14
|
* Fixed rowcount for SELECT statements. They're -1 now (again), for better ↵Gerhard Häring2008-05-311-0/+9
| | | | DB-API 2.0 compliance.
* Implemented feature request 2157: Converter names are cut off at '('Gerhard Häring2008-05-041-1/+16
| | | | | | 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-0/+20
| | | | sqlite3.Row type is now correctly hashable.
* Prevent test_sqlite from hanging on older versions of sqlite.Neal Norwitz2008-04-051-0/+8
| | | | | | | | | | The problem is that when trying to do the second insert, sqlite seems to sleep for a very long time. Here is the output from strace: read(6, "SQLite format 3\0\4\0\1\1\0@ \0\0\0\1\0\0\0\0"..., 1024) = 1024 nanosleep({4294, 966296000}, <unfinished ...> I don't know which version this was fixed in, but 3.2.1 definitely fails.
* These svn adds were forgotten in r62000Gregory P. Smith2008-03-281-0/+52
|
* Update sqlite3 module to match current version of pysqlite.Gerhard Häring2008-03-282-2/+2
|
* Catch OSError when trying to remove a file in case removal fails. ThisNeal Norwitz2008-03-051-2/+5
| | | | should prevent a failure in tearDown masking any real test failure.
* Made sqlite3 module's regression tests work with SQLite versions that don'tGerhard Häring2008-03-021-2/+3
| | | | support "create table if not exists", yet.
* Updated to pysqlite 2.4.1. Documentation additions will come later.Gerhard Häring2008-02-296-11/+295
|
* Patch #2167 from calvin: Remove unused importsChristian Heimes2008-02-231-1/+1
|
* Fix an odd error which would only occur close to new year's eve, dueGuido van Rossum2008-01-011-2/+1
| | | | | | to use of datetime.datetime.now() instead of utcnow() for comparison. (I think the test can still fail if it's executed pretty much *at* new year's eve, but that's not worth fixing.)
* Merged changes from standalone version 2.3.3. This should probably all beGerhard Häring2007-01-143-5/+55
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* The sqlite3 module did cut off data from the SQLite database at the first nullGerhard Häring2006-07-021-2/+20
| | | | character before sending it to a custom converter. This has been fixed now.
* Removed call to enable_callback_tracebacks that slipped in by accident.Gerhard Häring2006-06-211-1/+0
|
* Re-revert this change. Install the version check and don't run the testNeal Norwitz2006-06-151-0/+2
| | | | | | | until Gerhard has time to fully debug the issue. This affects versions before 3.2.1 (possibly only versions earlier than 3.1.3). Based on discussion on python-checkins.
* Speculative checkin (requires approval of Gerhard Haering)Neal Norwitz2006-06-152-12/+0
| | | | | | | | | 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-142-0/+12
| | | | | | | | | | | 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.
* Whitespace normalization.Tim Peters2006-06-141-1/+1
|
* Merged changes from external pysqlite 2.3.0 release. Documentation updates willGerhard Häring2006-06-133-37/+109
| | | | 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-233-3/+42
|
* Update to pysqlite 2.2.0Anthony Baxter2006-04-044-1/+172
|
* merged the sqlite-integration branch.Anthony Baxter2006-04-016-0/+1713
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.