Differences between revisions 96 and 113 (spanning 17 versions)
⇤ ← Revision 96 as of 2008-12-07 09:13:24 →
Size: 4208
Editor: pool-72-83-83-34
Comment: Separated Sybase ASE and Sybase SQL Anywhere and linked to SQL Anywhere native module
← Revision 113 as of 2020-12-09 09:29:13 → ⇥
Size: 2681
Editor: MarcAndreLemburg
Comment: Add InterSystems IRIS
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
The contents of this page are being merged into the ChoosingDatabase page. This page lists database interfaces available for Python. It may also help in finding a suitable database engine for you to use in your Python database applications.
Line 5: Line 5:
= Relational database =
Line 7: Line 6:
Databases based on a relational model, with support for SQL. = Generic Database Interfaces and APIs =
Line 9: Line 8:
== ODBC ==
Line 11: Line 9:
ODBC allows you to use a single library and API to connect to many different databases, including most of those below.  * The Python standard for database interfaces is the [[http://www.python.org/dev/peps/pep-0249/|Python DB-API (PEP 249)]] Most Python database interfaces adhere to this standard.
Line 13: Line 11:
 * pyodbc: http://code.google.com/p/pyodbc Open source, mature DB API library  * Most databases have ODBC support; see the section below on ODBC modules.
 * Java databases usually support JDBC, and can be used from Jython.
 * See also [[DbApiModuleComparison|DbApiModuleComparison]]
Line 15: Line 15:
== MySQL ==
 * mysql-python: http://sourceforge.net/projects/mysql-python
Line 18: Line 16:
== PostgreSQL == == ODBC Support ==
Line 20: Line 18:
 * psycopg
  * psycopg1: http://initd.org/projects/psycopg1
  * psycopg2: http://initd.org/projects/psycopg2
Line 24: Line 19:
 * pyPgSQL: http://pypgsql.sourceforge.net/  * See [[ODBC|ODBC]]
Line 26: Line 21:
 * PyGreSQL: http://www.pygresql.org/
Line 28: Line 22:
 * PoPy: http://sourceforge.net/projects/popy
  * PoPy and PyGreSQL are [[http://www.zope.org/Members/tm/Full_Announce|merging]]		 == ADO Support ==
Line 31: Line 24:
 * pg/python: http://python.projects.postgresql.org/
  * pg_proboscis: DB-API 2.0 and GreenTrunk Interfaces http://python.projects.postgresql.org/project/pg_proboscis.html
  * pg_pqueue: PQ 3.0 Protocol elements http://python.projects.postgresql.org/project/pg_pqueue.html
Line 35: Line 25:
 * pgasync: http://jamwt.com/pgasync/
  * Asynchronous and pure Python. Speed comparable to C bindings. Special support for Twisted.		  * See [[ADO|ADO]]
Line 38: Line 27:
 * bpgsql: http://barryp.org/software/bpgsql/
  * Barebones pure-Python PostgreSQL client
Line 41: Line 28:
 * [[sipPQ]] = Database Interfaces for Relational Database Systems =
Line 43: Line 30:
 * mxODBC: http://www.egenix.com/products/python/mxODBC/
  * Supports the [[http://www.postgresql.org/ftp/odbc/versions/|PostgreSQL ODBC driver]] on both Windows and Unix.
Note that you have to enable the advanced option "Use bytea for lo" in case you want to work with BLOBs.
Line 47: Line 31:
== Oracle == Database systems employing a relational model, with support for SQL.
Line 49: Line 33:
 * cx_Oracle: http://www.python.net/crew/atuining/cx_Oracle/
Line 51: Line 34:
 * DCOracle: http://www.zope.org/Products/DCOracle/
  * This is for old Oracle versions (7 and 8).		 == General Purpose Database Systems ==
Line 54: Line 36:
 * DCOracle2: http://www.zope.org/Members/matt/dco2
  * For Oracle 8i and up.		  * IBM [[DB2|DB2]]
 * [[Firebird|Firebird]] (and Interbase)
 * [[Informix|Informix]]
 * [[Ingres|Ingres]]
 * [[MySQL|MySQL]]
 * [[Oracle|Oracle]]
 * [[PostgreSQL|PostgreSQL]]
 * [[SAP DB|SAP DB]] (also known as "MaxDB")
 * Microsoft [[SQL Server|SQL Server]]
 * Microsoft [[Microsoft Access|Access]]
 * [[Sybase|Sybase]]
 * [[InterSystems IRIS]]
Line 57: Line 49:
 * mxODBC: http://www.egenix.com/products/python/mxODBC/
  * Supports the [[http://www.oracle.com/technology/tech/oci/instantclient/index.html|Oracle Instant Client]] which is available for Windows and many popular Unix platforms.		 (To add new entries, please choose [[DatabaseTemplate|DatabaseTemplate]] when creating the page.)
Line 60: Line 51:
== IBM DB2 == == Data Warehouse Database Systems ==
Line 62: Line 53:
 * More info on [[DB2]]  * [[Teradata|Teradata]]
 * IBM [[Netezza|Netezza]]
Line 64: Line 56:
== Sybase ASE == (To add new entries, please choose [[DatabaseTemplate|DatabaseTemplate]] when creating the page.)
Line 66: Line 58:
 * sybase
  * old: http://www.object-craft.com.au/projects/sybase/
  * new: http://python-sybase.sourceforge.net/		 == Database Systems for Embedding Into Applications ==
Line 70: Line 60:
 * mxODBC: http://www.egenix.com/products/python/mxODBC/
  * Supports Sybase ASE.
Line 73: Line 61:
== Sybase SQL Anywhere == The following database systems are more oriented towards embedded applications:
Line 75: Line 63:
 * sqlanydb: http://dcx.sybase.com/1100en/dbprogramming_en11/pg-python.html
  * Implements with extensions Database API 2.0
Line 78: Line 64:
 * mxODBC: http://www.egenix.com/products/python/mxODBC/
  * Supports SQL Anywhere.		  * [[asql|asql]]
 * [[GadFly|GadFly]]
 * [[SQLite|SQLite]]
 * [[ThinkSQL|ThinkSQL]]
Line 81: Line 69:
== MaxDB/SAPDB ==
Line 83: Line 70:
 * sdb: http://help.sap.com/saphelp_nw04s/helpdata/en/3c/5c02409d59ea69e10000000a155106/frameset.htm (To add new entries, please choose [[DatabaseTemplate|DatabaseTemplate]] when creating the page.)
Line 85: Line 72:
 * mxODBC: http://www.egenix.com/products/python/mxODBC/
  * MaxDB/SAPDB's native CLI is ODBC compatible and mxODBC can link directly against the CLI libs on Unix. It also supports the ODBC driver on Windows.
Line 88: Line 73:
== Informix == = Non-Relational Databases =
Line 90: Line 75:
 * InformixDB: http://informixdb.sourceforge.net/
Line 92: Line 76:
 * mxODBC: http://www.egenix.com/products/python/mxODBC/
  * Note: The Informix ODBC drivers are included in the Informix CSDK.		 == Record-based Databases ==
Line 95: Line 78:
== Ingres ==
Line 97: Line 79:
 * ingresdbi: http://www.ingres.com Databases working on flat files or fixed records.
Line 99: Line 81:
== Microsoft SQL Server ==
Line 101: Line 82:
 * See [[SQL Server]]  * [[MetaKit|MetaKit]]
 * [[ZODB|ZODB]]
 * [[BerkeleyDB|BerkeleyDB]]
 * [[KirbyBase|KirbyBase]]
 * [[Durus|Durus]]
 * [[atop|atop]]
 * [[buzhug|buzhug]]


(To add new entries, please choose [[DatabaseTemplate|DatabaseTemplate]] when creating the page.)


== XML Databases ==


 * 4Suite server
 * Oracle/Sleepycat DB XML ([[http://jimmyg.org/blog/2008/oracle-db-xml-was-sleepycat.html|howto]])


== Graph Databases ==


 * [[Neo4j|Neo4j]]


(To add new entries, please choose [[DatabaseTemplate|DatabaseTemplate]] when creating the page.)
Line 105: Line 112:
== buzhug ==
Line 107: Line 113:
[[http://buzhug.sourceforge.net/|buzhug]] is a pure-Python database engine, using a Pythonic, no-SQL syntax.

The data is stored and accessed on disk (it is not an in-memory database). The implementation has been designed to make all operations, and especially selection, as fast as possible with an interpreted language.

A limited benchmark using the same use cases as SQLite's author shows that buzhug is much faster than other pure-Python modules (KirbyBase, gadfly). SQLite, which is implemented in C, is faster, but only less than 3 times on the average.

== SnakeSQL ==

[[http://www.pythonweb.org/projects/snakesql/|SnakeSQL]] is a pure Python SQL database written to remove the dependence of the Python Web Modules on 3rd party drivers for non-Python databases like MySQL but designed to be a useful database in its own right.		  * [[buzhug|buzhug]]
 * [[SnakeSQL|SnakeSQL]]

Contents

  1. Generic Database Interfaces and APIs
    1. ODBC Support
    2. ADO Support
  2. Database Interfaces for Relational Database Systems
    1. General Purpose Database Systems
    2. Data Warehouse Database Systems
    3. Database Systems for Embedding Into Applications
  3. Non-Relational Databases
    1. Record-based Databases
    2. XML Databases
    3. Graph Databases
  4. Native Python Databases

This page lists database interfaces available for Python. It may also help in finding a suitable database engine for you to use in your Python database applications.

Generic Database Interfaces and APIs

  • The Python standard for database interfaces is the Python DB-API (PEP 249) Most Python database interfaces adhere to this standard.

  • Most databases have ODBC support; see the section below on ODBC modules.
  • Java databases usually support JDBC, and can be used from Jython.

  • See also DbApiModuleComparison

ODBC Support

ADO Support

Database Interfaces for Relational Database Systems

Database systems employing a relational model, with support for SQL.

General Purpose Database Systems

(To add new entries, please choose DatabaseTemplate when creating the page.)

Data Warehouse Database Systems

(To add new entries, please choose DatabaseTemplate when creating the page.)

Database Systems for Embedding Into Applications

The following database systems are more oriented towards embedded applications:

(To add new entries, please choose DatabaseTemplate when creating the page.)

Non-Relational Databases

Record-based Databases

Databases working on flat files or fixed records.

(To add new entries, please choose DatabaseTemplate when creating the page.)

XML Databases

  • 4Suite server

  • Oracle/Sleepycat DB XML (howto)

Graph Databases

(To add new entries, please choose DatabaseTemplate when creating the page.)

Native Python Databases

DatabaseInterfaces (last edited 2020-12-09 09:29:13 by MarcAndreLemburg)

Unable to edit the page? See the FrontPage for instructions.