view Modules/_sqlite/util.c @ 56797:ccbf7ebef475 2.6

Recorded merge of revisions 69159,69161,69240,69271-69273,69276 via svnmerge from svn+ssh://pythondev@svn.python.org/python/trunk ........ r69159 | gregory.p.smith | 2009-02-01 01:16:01 +0100 (So, 01 Feb 2009) | 2 lines Update doc wording as suggested in issue4903. ........ r69161 | gregory.p.smith | 2009-02-01 01:24:21 +0100 (So, 01 Feb 2009) | 2 lines wording for for issue4903. ........ r69240 | raymond.hettinger | 2009-02-03 04:18:14 +0100 (Di, 03 Feb 2009) | 1 line Record operator deprecations in docs. ........ r69271 | raymond.hettinger | 2009-02-04 11:52:32 +0100 (Mi, 04 Feb 2009) | 1 line Minor doc fixups. ........ r69272 | raymond.hettinger | 2009-02-04 12:14:18 +0100 (Mi, 04 Feb 2009) | 1 line Doc fixes. Remove overbroad, redundant warnings. Fixup example code. ........ r69273 | raymond.hettinger | 2009-02-04 12:31:30 +0100 (Mi, 04 Feb 2009) | 1 line Tweak the docs for Counter() objects. ........ r69276 | raymond.hettinger | 2009-02-04 20:25:17 +0100 (Mi, 04 Feb 2009) | 1 line Clarify that named tuples do not have to subclass tuple. ........
author Georg Brandl <georg@python.org>
date Tue, 27 Oct 2009 13:29:01 +0000
parents 4c77d1016f60
children 787b969d37f0 04d3ae52ff73
line wrap: on
line source

/* util.c - various utility functions
 *
 * Copyright (C) 2005-2007 Gerhard Häring <gh@ghaering.de>
 *
 * This file is part of pysqlite.
 *
 * This software is provided 'as-is', without any express or implied
 * warranty.  In no event will the authors be held liable for any damages
 * arising from the use of this software.
 *
 * Permission is granted to anyone to use this software for any purpose,
 * including commercial applications, and to alter it and redistribute it
 * freely, subject to the following restrictions:
 *
 * 1. The origin of this software must not be misrepresented; you must not
 *    claim that you wrote the original software. If you use this software
 *    in a product, an acknowledgment in the product documentation would be
 *    appreciated but is not required.
 * 2. Altered source versions must be plainly marked as such, and must not be
 *    misrepresented as being the original software.
 * 3. This notice may not be removed or altered from any source distribution.
 */

#include "module.h"
#include "connection.h"

int pysqlite_step(sqlite3_stmt* statement, pysqlite_Connection* connection)
{
    int rc;

    if (statement == NULL) {
        /* this is a workaround for SQLite 3.5 and later. it now apparently
         * returns NULL for "no-operation" statements */
        rc = SQLITE_OK;
    } else {
        Py_BEGIN_ALLOW_THREADS
        rc = sqlite3_step(statement);
        Py_END_ALLOW_THREADS
    }

    return rc;
}

/**
 * Checks the SQLite error code and sets the appropriate DB-API exception.
 * Returns the error code (0 means no error occurred).
 */
int _pysqlite_seterror(sqlite3* db, sqlite3_stmt* st)
{
    int errorcode;

    /* SQLite often doesn't report anything useful, unless you reset the statement first */
    if (st != NULL) {
        (void)sqlite3_reset(st);
    }

    errorcode = sqlite3_errcode(db);

    switch (errorcode)
    {
        case SQLITE_OK:
            PyErr_Clear();
            break;
        case SQLITE_INTERNAL:
        case SQLITE_NOTFOUND:
            PyErr_SetString(pysqlite_InternalError, sqlite3_errmsg(db));
            break;
        case SQLITE_NOMEM:
            (void)PyErr_NoMemory();
            break;
        case SQLITE_ERROR:
        case SQLITE_PERM:
        case SQLITE_ABORT:
        case SQLITE_BUSY:
        case SQLITE_LOCKED:
        case SQLITE_READONLY:
        case SQLITE_INTERRUPT:
        case SQLITE_IOERR:
        case SQLITE_FULL:
        case SQLITE_CANTOPEN:
        case SQLITE_PROTOCOL:
        case SQLITE_EMPTY:
        case SQLITE_SCHEMA:
            PyErr_SetString(pysqlite_OperationalError, sqlite3_errmsg(db));
            break;
        case SQLITE_CORRUPT:
            PyErr_SetString(pysqlite_DatabaseError, sqlite3_errmsg(db));
            break;
        case SQLITE_TOOBIG:
            PyErr_SetString(pysqlite_DataError, sqlite3_errmsg(db));
            break;
        case SQLITE_CONSTRAINT:
        case SQLITE_MISMATCH:
            PyErr_SetString(pysqlite_IntegrityError, sqlite3_errmsg(db));
            break;
        case SQLITE_MISUSE:
            PyErr_SetString(pysqlite_ProgrammingError, sqlite3_errmsg(db));
            break;
        default:
            PyErr_SetString(pysqlite_DatabaseError, sqlite3_errmsg(db));
            break;
    }

    return errorcode;
}