|
Size: 4324
Comment:
|
Size: 4752
Comment: wiki restore 2013-01-23
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| 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. | 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. |
| Line 4: | Line 6: |
| Line 8: | Line 11: |
| * DbObj: ORM | * [[DbObj|DbObj]]: ORM |
| Line 11: | Line 14: |
| * MiddleKit: ORM | * [[http://gthc.org/documentation/libschevo/|libschevo]]: Next-generation Object-Oriented DBMS based on Schevo. * [[MiddleKit|MiddleKit]]: ORM |
| Line 14: | Line 18: |
| * PyDo: ORM | * [[http://docs.projexsoftware.com/api/orb|ORB]]: easy to use ORM with Pythonic query markup language for multiple databases, works with the [[http://www.projexsoftware.com/products/orbiter|Orbiter]] ORM designer * [[PyDo|PyDo]]: ORM |
| Line 20: | Line 25: |
| Line 21: | Line 27: |
| Line 26: | Line 33: |
| * [[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. | * [[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. |
| Line 28: | Line 35: |
| * PyTable * 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. |
* [[PyTable|PyTable]] * The [[PythonWebModules|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|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. |
| Line 37: | Line 44: |
| Line 38: | Line 46: |
| Line 42: | Line 51: |
| See also Thinki:PersistenceSystems and Thinki:ObjectOrientedDatabase | See also Thinki:PersistenceSystems and Thinki:ObjectOrientedDatabase |
| Line 46: | Line 56: |
| Line 47: | Line 58: |
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.
dal.py: a Database Abstraction Layer (DAL), an API that maps Python objects into database objects such as queries, tables, and records. 101 video (This module is normally distributed as part of web2py but it does not depend on web2py, except for few some web2py specific functionalities)
DbObj: ORM
Dejavu: Public domain, thread-safe, Data Mapper ORM. (latest rel. 1.5 dd. 2007-01-24)
forgetSQL: ORM
libschevo: Next-generation Object-Oriented DBMS based on Schevo.
MiddleKit: ORM
Modeling Object-Relational Bridge: ORM and schema design with Zope integration
ORB: easy to use ORM with Pythonic query markup language for multiple databases, works with the Orbiter ORM designer
PyDo: ORM
quick_orm: ORM on top of SQLAlchemy to make things simple
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.