#33483: Index name migration instability between database engines
-------------------------------------+-------------------------------------
Reporter: Marti Raudsepp | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 4.0
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
oracle,migrations,indexes | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Marti Raudsepp):
> I really would like to unify this, however we cannot do this without a
backward compatible solution.
I agree, backwards compatibility is important. Isn't this the right place
to come up with options how to do it in a backward-compatible manner?
But you seem to be shutting down the path forward with "it's difficult,
therefore we won't fix it".
> Unfortunately, database backends (even builtin) will never be fully
swappable.
I didn't say "fully swappable", I recognize there are engine-specific
features.
But for models that use bare minimum ORM features (tables, columns,
indexes), isn't that something to strive for? There are so many Django
libraries and add-ons that rely on this assumption. This is one of the
most valuable parts of the Django ecosystem. Throwing it out is not
something the Django project should do lightly.
Otherwise, the fact that migrations aren't portable between engines should
be clearly documented, which it is not as far as I can tell.
--
Ticket URL: <https://code.djangoproject.com/ticket/33483#comment:6>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.99ad0aedf917d8ea03736d6b71c41fd4%40djangoproject.com.
