#24106: Document backwards incompatible changes to database backend API
-------------------------------------+-------------------------------------
Reporter: akaariai | Owner: nobody
Type: New | Status: new
feature |
Component: Database | Version: master
layer (models, ORM) |
Severity: Release | Keywords:
blocker |
Triage Stage: Accepted | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
I believe we don't have a separate ticket for documenting backwards
incompatible changes to database backend API. In duth it was agreed that
we want to do this.
An idea of how to do this is to log/diff changes to Django's backends
between stable/1.7 and master. Going through the changes in Django should
give a good approximation of all the breaking changes (another place where
breakage is possible is Compiler module).
If possible, I'd like to document the changes in a way that is both
backwards and forwards compatible. That is, we give a replacement
suggestion that works both in 1.7 and 1.8 (very likely conditional on
Django version).
--
Ticket URL: <https://code.djangoproject.com/ticket/24106>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/051.1fe6c5c614ee3aa182b3d2bd71ed0f6d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
