Differences between revisions 57 and 96 (spanning 39 versions)
⇤ ← Revision 57 as of 2006-09-08 09:22:33 →
Size: 6277
Editor: 211
Comment: Delete SnakeDb
← 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
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
[[TableOfContents]] <<TableOfContents>>
Line 3: Line 3:
= See also =
 * ChoosingDatabase
 * DbApiModuleComparison
 * HigherLevelDatabaseProgramming
 * http://www.python.org/topics/database/modules.html
 * [http://dmoz.org/Computers/Programming/Languages/Python/Modules/Databases_and_Persistence/ Category in the Open Directory Project]		 The contents of this page are being merged into the ChoosingDatabase page.
Line 11: Line 6:
Databases based on relational model, with support for SQL.
Databases based on a relational model, with support for SQL.

== ODBC ==

ODBC allows you to use a single library and API to connect to many different databases, including most of those below.

 * pyodbc: http://code.google.com/p/pyodbc Open source, mature DB API library
Line 14: Line 16:
 * MySQLdb: http://dev.mysql.com/downloads/python.html  * mysql-python: http://sourceforge.net/projects/mysql-python
Line 17: Line 19:
Line 20: Line 23:
Line 21: Line 25:
 * ["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/
 * PyGreSQL: http://www.pygresql.org/

 * PoPy: http://sourceforge.net/projects/popy
  * PoPy and PyGreSQL are [[http://www.zope.org/Members/tm/Full_Announce|merging]]

 * 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 26: Line 37:
Line 29: Line 41:
== SQLite ==
 * pysqlite: http://pysqlite.org/
  * Have versions for both SQLite 2 and 3.
 * APSW: http://www.rogerbinns.com/apsw.html
  * SQLite 3 only.
  * Not DBAPI compliant. Focus on wrapping all SQLite APIs.		  * [[sipPQ]]

 * 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 37: Line 48:
Line 38: Line 50:
Line 40: Line 53:
Line 43: Line 57:
== Firebird/Interbase ==
 * KInterbasDB: http://kinterbasdb.sourceforge.net/		  * 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.
Line 46: Line 60:
== Sybase ==
 * by Dave Cole: http://www.object-craft.com.au/projects/sybase/		 == IBM DB2 ==
Line 49: Line 62:
== MSSQL ==
 * by Dave Cole: http://www.object-craft.com.au/projects/mssql/
 * pymssql: http://pymssql.sourceforge.net/		  * More info on [[DB2]]
Line 53: Line 64:
== DB2 ==
 * PyDB2: http://sourceforge.net/projects/pydb2		 == Sybase ASE ==
Line 56: Line 66:
== MaxDB/SAP DB ==
 * http://dev.mysql.com/doc/maxdb/interfaces.html		  * sybase
  * old: http://www.object-craft.com.au/projects/sybase/
  * new: http://python-sybase.sourceforge.net/
Line 59: Line 70:
== ThinkSQL ==
 * Pure Python DB-API 2.0 module: http://www.thinksql.com/		  * mxODBC: http://www.egenix.com/products/python/mxODBC/
  * Supports Sybase ASE.

== Sybase SQL Anywhere ==

 * sqlanydb: http://dcx.sybase.com/1100en/dbprogramming_en11/pg-python.html
  * Implements with extensions Database API 2.0

 * mxODBC: http://www.egenix.com/products/python/mxODBC/
  * Supports SQL Anywhere.

== MaxDB/SAPDB ==

 * sdb: http://help.sap.com/saphelp_nw04s/helpdata/en/3c/5c02409d59ea69e10000000a155106/frameset.htm

 * 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 63: Line 89:
Line 65: Line 92:
 * mxODBC: http://www.egenix.com/products/python/mxODBC/
  * Note: The Informix ODBC drivers are included in the Informix CSDK.
Line 66: Line 96:
 * http://ingres.com/products/Prod_Download_Drivers.html
Line 68: Line 97:
== ODBC ==
 * pyodbc: http://pyodbc.sourceforge.net/
 * mxODBC: http://www.egenix.com/files/python/mxODBC.html		  * ingresdbi: http://www.ingres.com
Line 72: Line 99:
== ADO ==
 * adodbapi: http://adodbapi.sourceforge.net/		 == Microsoft SQL Server ==

 * See [[SQL Server]]
Line 77: Line 105:
== Gadfly ==
Gadfly is a simple relational database system implemented in Python based on the SQL Structured Query Language.		 == buzhug ==
Line 80: Line 107:
http://gadfly.sourceforge.net/ [[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.
Line 83: Line 114:
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 85: Line 115:
http://www.pythonweb.org/projects/snakesql/

== ZODB ==
Zope Object Database.

 * http://www.zope.org/Wikis/ZODB/FrontPage
 * DirectoryStorage: http://dirstorage.sourceforge.net/
 * PGStorage: http://hathawaymix.org/Software/PGStorage

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

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

== xsdbXML ==
http://xsdb.sourceforge.net/

= 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://orm.nongnu.org/ ORM] ([http://freshmeat.net/projects/orm/ Freshmeat entry]) 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.

QLime ([http://freshmeat.net/projects/qlime/ Freshmeat entry]) Easy to use, transparent data access to relational databases or other data sources. See examples here: http://www.qlime.org/example.rst '''Note: qlime.org does not currently provide the QLime site'''

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

Contents

  1. Relational database
    1. ODBC
    2. MySQL
    3. PostgreSQL
    4. Oracle
    5. IBM DB2
    6. Sybase ASE
    7. Sybase SQL Anywhere
    8. MaxDB/SAPDB
    9. Informix
    10. Ingres
    11. Microsoft SQL Server
  2. Native Python Databases
    1. buzhug
    2. SnakeSQL

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

Relational database

Databases based on a relational model, with support for SQL.

ODBC

ODBC allows you to use a single library and API to connect to many different databases, including most of those below.

MySQL

PostgreSQL

Note that you have to enable the advanced option "Use bytea for lo" in case you want to work with BLOBs.

Oracle

IBM DB2

  • More info on DB2

Sybase ASE

Sybase SQL Anywhere

MaxDB/SAPDB

Informix

Ingres

Microsoft SQL Server

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.

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

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