#22784: Schema migration: rename tables
-------------------------------------+-------------------------------------
Reporter: maxi | Owner: nobody
Type: | Status: closed
Cleanup/optimization | Version:
Component: Migrations | 1.7-beta-2
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by andrewgodwin):
* status: new => closed
* resolution: => wontfix
Comment:
Unfortunately, I think the correct thing for the backend to do here is the
same as the SQLite backend - emulate the rename by making a new table and
copying data across. SQLite also doesn't allow renames, but people expect
certain stuff, so we had to emulate it.
Closing this as WONTFIX for now. If doing that proves unbelievably
difficult, we could reopen and consider not supporting it as a feature
flag, but that would mean that Firebird can't run some migrations (table
rename is assumed to be possible by the autodetector, and as migrations
are baked and shipped we can't have the autodetector change behaviour
based on target database, as it doesn't know what the target is)
--
Ticket URL: <https://code.djangoproject.com/ticket/22784#comment:5>
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/062.5834cd78c0fba6cb424aa857f9ede9e9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
