#22784: Schema migration: rename tables
-------------------------------+--------------------------------------
Reporter: maxi | Owner: nobody
Type: Uncategorized | Status: new
Component: Migrations | Version: 1.7-beta-2
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by shai):
Sometimes backends do things that the engine proper doesn't support by
performing extra work -- the Sqlite backend, as a prime example, recreates
tables as an implementation of alter-column; the usually-saner Oracle
backend jumps through hoops to change a column from TextField to CharField
or vice-versa, which isn't supported by the Oracle database.
Introducing the flag as requested here means that table-renaming is an
optional feature of schema editors. That may be acceptable, or not -- I'm
not even sure what I think of it. I think it may be worth a discussion on
the DevelopersMailingList.
--
Ticket URL: <https://code.djangoproject.com/ticket/22784#comment:3>
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.406c4a2922bf24a6f0569ee2fb0e469f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
