#33185: sqlmigrate crashes given a RenameModel operation with a self-referencing
foreign key on MySQL
-----------------------------+------------------------------------
Reporter: Jacob Walls | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: dev
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+------------------------------------
Comment (by David Wobrock):
Replying to [comment:2 Simon Charette]:
> there's no way we can get `sqlmigrate` to be foolproof while having the
schema editor rely on introspection
I completely agree with this statement, and it would be interesting to try
and address it.
> either commit to not using introspection in schema editor and making
`sqlmigrate` a first class citizen that doesn't require a database
connection
But I'm wondering if that is even possible. I have the impression that
many objects and names created in DB by Django can be vendor specific. And
if we don't establish a DB connection (to know the vendor and the DB
version), we cannot deterministically know the names used and allowed in
the database.
It would probably be very interesting to have such a common and
predictable ground across supported database, but backward compatibility
might bite us when trying to commonise it - and I'm not even sure it's
possible.
--
Ticket URL: <https://code.djangoproject.com/ticket/33185#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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070182bccaf3f5-608bcbf7-dd5f-444f-9a92-c339d388be9e-000000%40eu-central-1.amazonses.com.
