93 | | |
94 | | == Alternative Ideas for Database Independence |
95 | | |
96 | | === Object-Relational Mapper |
97 | | |
98 | | An ORM could be used to provide a unified object interface to different RDBMS: |
99 | | * [http://modeling.sourceforge.net/ Modeling], which is another, more advanced OR-Mapper. |
100 | | * [http://adodb.sourceforge.net ADODB], the fast database abstraction layer with a version available for Python. |
101 | | * [http://www.sqlalchemy.org/ SQLAlchemy] is also quite advanced. |
102 | | * Some people have been talking about using [http://sqlobject.org SQLObject] to accomplish this goal of database independence. |
103 | | |
104 | | === Store Tickets and Wiki pages directly in the Subversion repository |
105 | | |
106 | | 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]. |
107 | | |
108 | | ---- |
109 | | See also: SqlAlchemy |