At my local django installation, changing the max_length of a charfield
did result in the correct migrations (a.k. 0010_autocreated....py), but
migrating the changes to the Sqlite database did not change the varchar in
the database to the new max_length.
--
Ticket URL: <https://code.djangoproject.com/ticket/27341>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
I see I've filed a similar bug before: #25866
Would be nice to have it fixed, although I understand it does not have the
highest priority.
--
Ticket URL: <https://code.djangoproject.com/ticket/27341#comment:1>
* component: Database layer (models, ORM) => Migrations
* easy: 1 => 0
Comment:
Doesn't SQLite [http://www.sqlite.org/faq.html#q9 ignore any size limit on
the column] anyway?
--
Ticket URL: <https://code.djangoproject.com/ticket/27341#comment:2>
* status: new => closed
* resolution: => worksforme
Comment:
Regardless of my last comment, I see a change from `varchar(200)` to
`varchar(201)` in the "SQLite Database Browser" program after changing the
length of `CharField` and running the migration. Please reopen if you can
provide steps on how to reproduce.
--
Ticket URL: <https://code.djangoproject.com/ticket/27341#comment:3>