| | 1 | = Alternative Ideas for Database Independence |
| | 2 | |
| | 3 | == Object-Relational Mapper |
| | 4 | |
| | 5 | An ORM could be used to provide a unified object interface to different RDBMS: |
| | 6 | * [http://modeling.sourceforge.net/ Modeling], which is another, more advanced OR-Mapper. |
| | 7 | * [http://adodb.sourceforge.net ADODB], the fast database abstraction layer with a version available for Python. |
| | 8 | * [http://www.sqlalchemy.org/ SQLAlchemy] is also quite advanced. |
| | 9 | * Some people have been talking about using [http://sqlobject.org SQLObject] to accomplish this goal of database independence. |
| | 10 | |
| | 11 | == Store Tickets and Wiki pages directly in the Subversion repository |
| | 12 | |
| | 13 | A compelling idea with many advantages. A page advocating this plan is TighterSubversionIntegration. There has also been a discussion on the Trac mailing list, of which the arguments are summarized on the page [wiki:WhySQLite WhySQLite]. |
| | 14 | |
| | 15 | ---- |
| | 16 | |
| | 17 | See also: SqlAlchemy |
