Differences between revisions 31 and 98 (spanning 67 versions)
Revision 31 as of 2006-09-05 11:10:21
Size: 5702
Editor: 211
Comment: pgasync
Revision 98 as of 2008-12-08 13:02:25
Size: 3758
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
  ''This page seems to duplicate ChoosingDatabase, wouldn't it be better to merge shelve and the rest there? -- DanielDittmar [[DateTime(2003-02-11T23:15:22)]]'' <<TableOfContents>>
Line 3: Line 3:
  ''I don't think so. Now they surely have to be refactored both, but ChoosingDatabase seems to be a good page for one place for categorized comparision to narrow novice's choice while that is merely a catalog. -- MikeRovner [[DateTime(2003-02-11T16:50:45)]]'' Note: The contents of the ChoosingDatabase page are being merged back into this page.
Line 5: Line 5:
  ''I seems missed DbApiModuleComparison page. Probably I better combine them with links from both places. -- MikeRovner [[DateTime()]]'' = Generic Database Interfaces and APIs =
Line 7: Line 7:
 * The Python standard for database interfaces is the [[http://www.python.org/dev/peps/pep-0249/|Python DB-API (PEP 249)]]
Line 8: Line 9:
 Most Python database interfaces adhere to this standard.
Line 9: Line 11:
[[TableOfContents]]  * 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
Line 11: Line 15:
See also HigherLevelDatabaseProgramming == ODBC Support ==
Line 13: Line 17:
= DBMS interfaces =
Things you connect to.
 * ceODBC: http://ceodbc.sourceforge.net
Line 16: Line 19:
Take a look at
http://www.python.org/topics/database/modules.html and
http://dmoz.org/Computers/Programming/Languages/Python/Modules/Databases_and_Persistence/.
 * pyodbc: http://pyodbc.sourceforge.net
Line 20: Line 21:
== MySQL ==
 * mysqldb module http://www.mysql.com/downloads/api-python.html
 * SnakeDb (http://www.scriptfoundry.com/modules/snakedb/)
 * [[http://www.egenix.com/products/python/mxODBC|mxODBC]]: A commercial Python extension that provides ODBC connectivity on Windows, Linux, Mac OS X, FreeBSD and many other Unix platforms.
Line 24: Line 23:
== PostgreSQL ==
 * psycopg (http://www.zope.org/Members/fog/psycopg) (!) preferable
  *important notes for psycopg
   *for commands that require running outside of a transaction use autocommit
    *ie conn.autocommit()
   *never commit on a cursor, always commit on a connection
 * pyPgSQL (http://pypgsql.sf.net/)
 * ["sipPQ"]
 * PyGreSQL (http://www.pygresql.org) and PoPy (http://sourceforge.net/projects/popy) are [http://archives.postgresql.org/pgsql-announce/2003-07/msg00002.php merging]
 * PostgresPy (http://python.projects.postgresql.org/)
 * pgasync (http://jamwt.com/pgasync/)
  * Asynchronous and pure Python. Speed comparable to C bindings. Special support for Twisted.
 * [[http://www.egenix.com/products/python/mxODBCConnect|mxODBC Connect]]: A commercial client-server product that allows connecting Python to ODBC compatible databases running on remote servers without requiring an ODBC driver on the client side.
Line 37: Line 25:
== Oracle ==  * ODBTPAPI: http://benjiyork.com/odbtp.html
Line 39: Line 27:
See ["Oracle"] for details, there are two choices:
 * dcOracle
 * cx_Oracle
== ADO Support ==
Line 43: Line 29:
== Sybase ==
module developed by Dave Cole http://www.object-craft.com.au/projects/sybase/
 * adodbapi (http://adodbapi.sourceforge.net/): A Python module that makes it easy to use Microsoft ADO for connecting to databases and other data sources.
Line 46: Line 31:
== MSSQL ==
module developed by Dave Cole http://www.object-craft.com.au/projects/mssql/
= Database Interfaces for Relational Database Systems =
Line 49: Line 33:
== BerkeleyDb == Database systems employing a relational model, with support for SQL.
Line 51: Line 35:
== ThinkSQL ==
 * Pure Python DB-API 2.0 module http://www.thinksql.co.uk
== General Purpose Database Systems ==
Line 54: Line 37:
== Informix ==
 * DB-API 2.0 module available here: http://informixdb.sourceforge.net/
 * IBM [[DB2]]
 * [[Firebird]] (and Interbase)
 * [[Informix]]
 * [[Ingres]]
 * [[MySQL]]
 * [[Oracle]]
 * [[PostgreSQL]]
 * [[SAP DB]] (also known as "MaxDB")
 * Microsoft [[SQL Server]]
 * [[Sybase]]

(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:

  * GadFly
  * [[SQLite]]
  * [[ThinkSQL]]

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

== Non-Relational Databases ==

  * MetaKit
  * [[ZODB]]
  * [[BerkeleyDB]]
  * [[KirbyBase]]
  * [[Durus]]
  * [[atop]]
  * [[buzhug]]
Line 59: Line 72:
== gadfly ==
Gadfly is a simple relational database system implemented in Python based on the SQL Structured Query Language.
Currently use C-extension module for speed. Pure Python version included.
http://gadfly.sourceforge.net/
== buzhug ==
Line 64: Line 74:
== ZODB ==
http://www.zope.org/Wikis/ZODB Zope Object DB
[[http://buzhug.sourceforge.net/|buzhug]] is a pure-Python database engine, using a Pythonic, no-SQL syntax.
Line 67: Line 76:
== shelve ==
A [http://www.python.org/doc/current/lib/module-shelve.html ''shelf''] is a persistent, dictionary-like object. The difference with ''dbm'' databases is that the values (not the keys!) in a shelf can be essentially arbitrary Python objects -- anything that the [http://www.python.org/doc/current/lib/module-pickle.html pickle] module can handle. This includes most class instances, recursive data types, and objects containing lots of shared sub-objects. The keys are ordinary strings.
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.
Line 70: Line 78:
== KirbyBase ==
http://www.netpromi.com/kirbybase.html
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.
Line 73: Line 80:
== SnakeSQL ==
Line 74: Line 82:
= Datafiles interfaces =
Things you open.
[[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.
Line 77: Line 84:
== xBase ==
Which stands for .dbf files interface.[[BR]]
.dbf files were produced by several old systems like dBase(II,III,IV), Fox(Base,Pro)
 * xBase (http://linux.techass.com/projects/xdb/) - Python interface in plans
 * http://www.fiby.at/dbfpy/index.html - working now. or (take it [http://starship.python.net/crew/jjkunce/python/dbfpy.tgz here])
 * http://www.sequiter.com/products/Python/
 * http://cbbrowne.com/info/xbase.html
 * http://www.e-bachmann.dk/docs/xbase.htm - dead link
-----
Line 86: Line 86:
== dbm ==
A family of old unix plain hash tables. Has varieties like dbm, ndbm, gdbm, dbmdb185.[[BR]]
See [http://www.python.org/doc/current/lib/module-anydbm.html anydbm],
[http://www.python.org/doc/current/lib/module-dumbdbm.html dumbdbm],
[http://www.python.org/doc/current/lib/module-dbhash.html dbhash],
[http://www.python.org/doc/current/lib/module-bsddb.html bsddb],
[http://www.python.org/doc/current/lib/module-dbm.html dbm],
[http://www.python.org/doc/current/lib/module-gdbm.html gdbm]
in Python Standard Library.
These entries still need to be merged into the resp. sub-pages:
Line 96: Line 88:
== MetaKit ==
http://www.equi4.com/metakit/python.html
== MaxDB/SAPDB ==
Line 99: Line 90:
== SQLite ==
Actualy it's a full-fleged SQL server, but embeddable. No external SQL server required. Think of Gadfly, only faster.
http://pysqlite.org/
 * sdb: http://help.sap.com/saphelp_nw04s/helpdata/en/3c/5c02409d59ea69e10000000a155106/frameset.htm
Line 103: Line 92:
= XML Databases or Interfaces =  * 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 105: Line 95:
== Forest == == Informix ==
Line 107: Line 97:
[http://cvs.infrae.com/forest/ Forest] is a (native) XML database written in Python. It is intended to
support fast queries of XML data.
 * InformixDB: http://informixdb.sourceforge.net/
Line 110: Line 99:
 * mxODBC: http://www.egenix.com/products/python/mxODBC/
  * Note: The Informix ODBC drivers are included in the Informix CSDK.
Line 111: Line 102:
== 4ODS == == Ingres ==
Line 113: Line 104:
http://www.4suite.org/


= Object-Relational Mappers =

[http://sqlobject.org SQLObject] is an object-relational mapper. It allows you to translate
RDBMS table rows into Python objects, and manipulate those objects to
transparently manipulate the database.

[http://www.tux4web.de/orm ORM] The Object Relational Membrane is a Python package that provides the functionality of an object relational layer like EJB or other persistence storage systems. It is a thin compatibility layer between SQL table layouts and Object Oriented Python. While providing a good deal of functionality, it tries to be as small and simple as possible. It works with PostgreSQL and MySQL.

[http://www.qlime.org/ QLime] Easy to use, transparent data access to relational databases or other data sources. See examples here: http://www.qlime.org/example.rst

See also HigherLevelDatabaseProgramming.

= Special file interface =

 * http://python-dsv.sourceforge.net/ CSV or any separated file (see also PEP:0305)
 * ConfigParser.py - Windows .ini format
 * gzip.py
 * zipfile.py
 * tar
 * pdf http://www.pythonware.com/
 * PyTables
 * ingresdbi: http://www.ingres.com

Note: The contents of the ChoosingDatabase page are being merged back into this page.

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.)

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

Native Python Databases

buzhug

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

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.


These entries still need to be merged into the resp. sub-pages:

MaxDB/SAPDB

Informix

Ingres

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

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