#6339 closed enhancement (wontfix)
Use django for multi database support
Reported by: | Owned by: | Jonas Borgström | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | general | Version: | |
Severity: | normal | Keywords: | django database |
Cc: | leho@… | Branch: | |
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
Didn't see this idea anywhere else, so I'm suggesting trac leverage django to abstract away its database queries. Django has support for PostgreSQL, MySQL, SQLite and Oracle, so you can make a lot of people happy without having to do all the work.
Of course, there is a lot of work converting all the queries to django api, but once you're done, your data model becomes much more hassle free.
I might consider volunteering for this to learn both django and trac better…
Attachments (0)
Change History (3)
comment:1 by , 17 years ago
comment:2 by , 17 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
Agree with wontfix.
Django is not a good candidate for being used as a database independence layer. It only adds oracle and mssql support to what we already have, plus it looks like you need the whole django package to get this working (django.db is not a self-contained sub-package).
SQLAlchemy seems to be a lot more appealing and I might have a try at reviving the sqlalchemy branch once 0.11 is out.
comment:3 by , 12 years ago
Cc: | added |
---|
There are plans for Trac to use SQL achemy or some alternative DB abstraction layer: see DatabaseBackend#AlternativeIdeasforDatabaseIndependence and sandbox/sqlalchemy for example.
Not sure how to close this ticket, as wontfix?