Differences between revisions 26 and 113 (spanning 87 versions)
Revision 26 as of 2005-09-13 21:48:32
Size: 5207
Editor: smtp
Comment:
Revision 113 as of 2020-12-09 09:29:13
Size: 2681
Comment: Add InterSystems IRIS
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)]]''

  ''I seems missed DbApiModuleComparison page. Probably I better combine them with links from both places. -- MikeRovner [[DateTime()]]''
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 8: Line 6:
= Generic Database Interfaces and APIs =
Line 9: Line 8:
[[TableOfContents]]
Line 11: Line 9:
See also HigherLevelDatabaseProgramming  * 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:
= DBMS interfaces =
Things you connect to.
 * 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 16: Line 15:
Take a look at
http://www.python.org/topics/database/modules.html and
http://dmoz.org/Computers/Programming/Languages/Python/Modules/Databases_and_Persistence/.
Line 20: Line 16:
== MySQL ==
 * mysqldb module http://www.mysql.com/downloads/api-python.html
 * SnakeDb (http://www.scriptfoundry.com/modules/snakedb/)
== ODBC Support ==
Line 24: Line 18:
== 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/)
Line 35: Line 19:
== Oracle ==  * See [[ODBC|ODBC]]
Line 37: Line 21:
See ["Oracle"] for details, there are two choices:
 * dcOracle
 * cx_Oracle
Line 41: Line 22:
== Sybase ==
module developed by Dave Cole http://www.object-craft.com.au/projects/sybase/
== ADO Support ==
Line 44: Line 24:
== MSSQL ==
Line 46: Line 25:
== BerkeleyDb ==  * See [[ADO|ADO]]
Line 48: Line 27:
== ThinkSQL ==
 * Pure Python DB-API 2.0 module http://www.thinksql.co.uk

= Database Interfaces for Relational Database Systems =


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


== General Purpose Database Systems ==

 * 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]]

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

== Data Warehouse Database Systems ==

 * [[Teradata|Teradata]]
 * IBM [[Netezza|Netezza]]

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

== Database Systems for Embedding Into Applications ==


The following database systems are more oriented towards embedded applications:


 * [[asql|asql]]
 * [[GadFly|GadFly]]
 * [[SQLite|SQLite]]
 * [[ThinkSQL|ThinkSQL]]


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


= Non-Relational Databases =


== Record-based Databases ==


Databases working on flat files or fixed records.


 * [[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 53: Line 112:
== 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/
Line 58: Line 113:
== ZODB ==
http://www.zope.org/Wikis/ZODB Zope Object DB

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

== KirbyBase ==
http://www.netpromi.com/kirbybase.html


= Datafiles interfaces =
Things you open.

== 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

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

== MetaKit ==
http://www.equi4.com/metakit/python.html

== SQLite ==
Actualy it's a full-fleged SQL server, but embeddable. No external SQL server required. Think of Gadfly, only faster.
http://pysqlite.org/

= XML Databases or Interfaces =

== Forest ==

[http://cvs.infrae.com/forest/ Forest] is a (native) XML database written in Python. It is intended to
support fast queries of XML data.


== 4ODS ==

http://www.4suite.org/


= Object-Relational Mappers =

== SQLObject ==

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



= 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
 * [[buzhug|buzhug]]
 * [[SnakeSQL|SnakeSQL]]

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.