#14686: ORM support for VoltDB
-------------------------------------+-------------------------------------
Reporter: sylverb | Owner: nobody
Type: Uncategorized | Status: closed
Component: Database layer | Version: master
(models, ORM) | Resolution: wontfix
Severity: Normal | Triage Stage:
Keywords: database, voltdb | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by russellm):
The exclusion wasn't "arbitrary" at all. Django has a database backend API
for a reason -- so that we don't need to be the maintainers for a thousand
database backends. We officially support the 3 most popular open source
databases, and one very high profile closed source database.
NoSQL has a branch because it was a Google Summer of Code project, and it
would have required significant architectural changes internally to make a
NoSQL backend possible. However, it's important to note that that branch
*didn't* proposed to add any new database backends. It was primarily a
series of internal changes that would make a third-party NoSQL backends
possible.
As for a list of external DB APIs -- the only list I can point you at
[https://docs.djangoproject.com/en/1.4/ref/databases/#using-a-3rd-party-
database-backend is in the docs]. We don't really have a firm set of
guidelines for what gets on this list; a rule of thumb would be "a backend
that someone is willing to state actually works in anger".
--
Ticket URL: <https://code.djangoproject.com/ticket/14686#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
