Russ is right, it's still open for changes, though I want to oversee any
changes very carefully because I want to make sure we ship something that
makes sense overall!
Altering column names is done as part of alter_field (if you look through
that huge method, you'll see it somewhere in there); cur
Trunk is still open for all 1.7 changes; 1.7 alpha is currently planned for
mid January, which is the cutoff point for major API changes; the beta a
month or so after that, which is the final cutoff for minor API changes.
On top of that - it looks like you're proposing a modification to the
schema
I just started to work on Django 1.7 support for django-mssql and I don't
remember if it's too far along to get API changes in for the schema editor?
I've hit a few road blocks with the current implementation of
BaseSchemaEditor. I've only just started to get up to speed with the new
changes, so pl