|
Size: 3474
Comment:
|
Size: 3818
Comment: converted to 1.6 markup
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 5: | Line 5: |
| * [http://www.nongnu.org/bazaar/ Bazaar ORM]: Easy to use and powerful abstraction layer between relational database and object oriented application. | * [[http://divmod.org/trac/wiki/DivmodAxiom|Axiom]]: MIT-licensed, SQLite-based * [[http://www.nongnu.org/bazaar/|Bazaar ORM]]: Easy to use and powerful abstraction layer between relational database and object oriented application. |
| Line 7: | Line 8: |
| * [http://projects.amor.org/dejavu Dejavu]: Public domain, thread-safe, Data Mapper ORM. * [http://forgetsql.sourceforge.net/ forgetSQL]: ORM |
* [[http://www.aminus.net/dejavu|Dejavu]]: Public domain, thread-safe, Data Mapper ORM. * [[http://forgetsql.sourceforge.net/|forgetSQL]]: ORM |
| Line 10: | Line 11: |
| * [http://modeling.sourceforge.net/ Modeling Object-Relational Bridge]: ORM and schema design with Zope integration * [http://orm.nongnu.org/ Object Relational Membrame] ([http://freshmeat.net/projects/orm/ Freshmeat entry]): ORM |
* [[http://modeling.sourceforge.net/|Modeling Object-Relational Bridge]]: ORM and schema design with Zope integration * [[http://orm.nongnu.org/|Object Relational Membrame]] ([[http://freshmeat.net/projects/orm/|Freshmeat entry]]): ORM |
| Line 13: | Line 14: |
| * [http://sqlobject.org/ SQLObject]: ORM * [http://www.sqlalchemy.org/ SQLAlchemy]: ORM toolkit * [https://storm.canonical.com Storm]: Clean and powerful ORM by Canonical. |
* [[http://sqlobject.org/|SQLObject]]: ORM * [[http://www.sqlalchemy.org/|SQLAlchemy]]: SQL Toolkit and ORM * [[https://storm.canonical.com|Storm]]: Clean and powerful ORM by Canonical. |
| Line 19: | Line 20: |
| * [http://opensource.theopalgroup.com/ db_row]: SQL result wrapper * [http://roundup.sf.net/ Roundup's hyperdb]: set of constrained data types with relations (many-to-many included) over multiple backends including SQL, metakit and db (yes, relations in an anydbm-backed database :) * [http://www.livinglogic.de/Python/sql/ ll.sql]: SQL generator * [http://pdo.neurokode.com PDO]: Python Database Objects - allows use of most DBAPI modules with a clean, simple API similar in scope to ADO or JDBC. Column access by name is provided by a low overhead mechanism. * PgResultSet: built-in facility for column access by name for pyPgSQL and PySQLite |
* [[http://opensource.theopalgroup.com/|db_row]]: SQL result wrapper * [[http://gnuenterprise.org/tools/common/|gnue-common]]: gnue.common.datasources module - Database abstraction layer * [[http://roundup.sf.net/|Roundup's hyperdb]]: set of constrained data types with relations (many-to-many included) over multiple backends including SQL, metakit and db (yes, relations in an anydbm-backed database :) * [[http://www.livinglogic.de/Python/sql/|ll.sql]]: SQL generator * [[http://pdo.neurokode.com|PDO]]: Python Database Objects - allows use of most DBAPI modules with a clean, simple API similar in scope to ADO or JDBC. Column access by name is provided by a low overhead mechanism. * [[https://fedorahosted.org/pySQLFace/|pySQLFace]]: SQL interface over DBAPI2. It provides a database specific API to retrive and save data by creating SQL/DML command objects from a configuration file. |
| Line 26: | Line 28: |
| * The PythonWebModules web.database.object module - Object relational mapper - treat an SQL database like python objects for easy programming, the SQL is done behind the scenes. Supports one and many to many mappings and can generate HTML forms for the data automatically. * 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-project.org/example.rst * [http://www.python.org/pypi/simpleQL simpleQL]: SQL generator using live translation of generator expressions * [http://py.vaults.ca/apyllo2.py/D21777795 SQLBuilder]: SQL generator * [http://dustman.net/andy/python/SQLDict SQLDict]: SQL wrapper * [http://lists.canonical.org/pipermail/kragen-hacks/2004-April/000394.html prototype SchemQL/Roe-like thing in Python] --- Python objects representing relational algebra expressions, backed by lazy compilation to SQL and an iterable interface. |
* The PythonWebModules web.database.object module - ORM - treat an SQL database like python objects for easy programming, the SQL is done behind the scenes. Supports one and many to many mappings and can generate HTML forms for the data automatically. * 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-project.org/example.rst * [[http://www.python.org/pypi/simpleQL|simpleQL]]: SQL generator using live translation of generator expressions * [[http://py.vaults.ca/apyllo2.py/D21777795|SQLBuilder]]: SQL generator * [[http://dustman.net/andy/python/SQLDict|SQLDict]]: SQL wrapper * [[http://lists.canonical.org/pipermail/kragen-hacks/2004-April/000394.html|prototype SchemQL/Roe-like thing in Python]] --- Python objects representing relational algebra expressions, backed by lazy compilation to SQL and an iterable interface. |
| Line 35: | Line 37: |
| * [http://www.quicksort.co.uk Dee]: A proposal to supersede SQL and the need for database sub-languages. Adds truly relational capabilities to Python (no wrappers, no mappers). | * [[http://www.quicksort.co.uk|Dee]]: A proposal to supersede SQL and the need for database sub-languages. Adds truly relational capabilities to Python (no wrappers, no mappers). |
There are several wrappers that provide improved or simplified interfaces to SQL databases. Some of these might be referred to as object relational mappers, or ORM in this list -- these create Pythonic objects out of database rows. Others may only help generate SQL, or provide simple mapping support.
Object Relational Mappers (ORMs)
Axiom: MIT-licensed, SQLite-based
Bazaar ORM: Easy to use and powerful abstraction layer between relational database and object oriented application.
DbObj: ORM
Dejavu: Public domain, thread-safe, Data Mapper ORM.
forgetSQL: ORM
MiddleKit: ORM
Modeling Object-Relational Bridge: ORM and schema design with Zope integration
PyDo: ORM
SQLObject: ORM
SQLAlchemy: SQL Toolkit and ORM
Storm: Clean and powerful ORM by Canonical.
SQL Wrappers & Generators
db_row: SQL result wrapper
gnue-common: gnue.common.datasources module - Database abstraction layer
Roundup's hyperdb: set of constrained data types with relations (many-to-many included) over multiple backends including SQL, metakit and db (yes, relations in an anydbm-backed database
ll.sql: SQL generator
PDO: Python Database Objects - allows use of most DBAPI modules with a clean, simple API similar in scope to ADO or JDBC. Column access by name is provided by a low overhead mechanism.
pySQLFace: SQL interface over DBAPI2. It provides a database specific API to retrive and save data by creating SQL/DML command objects from a configuration file.
The PythonWebModules web.database module - Database abstraction layer to make it possible to run the same SQL on different databases without changing your code.
The PythonWebModules web.database.object module - ORM - treat an SQL database like python objects for easy programming, the SQL is done behind the scenes. Supports one and many to many mappings and can generate HTML forms for the data automatically.
QLime (Freshmeat entry): Easy to use, transparent data access to relational databases or other data sources. See examples here: http://www.qlime-project.org/example.rst
simpleQL: SQL generator using live translation of generator expressions
SQLBuilder: SQL generator
SQLDict: SQL wrapper
prototype SchemQL/Roe-like thing in Python --- Python objects representing relational algebra expressions, backed by lazy compilation to SQL and an iterable interface.
Relational Python
Dee: A proposal to supersede SQL and the need for database sub-languages. Adds truly relational capabilities to Python (no wrappers, no mappers).
See also PersistenceSystems and ObjectOrientedDatabase
Editorial Notes
The above lists should be arranged in ascending alphabetical order - please respect this when adding new entries. When specifying release dates please use the format YYYY-MM-DD.