Re: [Django] #27341: Altering max_length on sqlite: makemigrations creates correct migration, but migrate does not alter length of varchar in de database itself

[Django]

#27341: Altering max_length on sqlite: makemigrations creates correct migration,
but migrate does not alter length of varchar in de database itself
+--
 Reporter:  Gerben Morsink  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.8
 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
+--
Changes (by Tim Graham):

 * 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: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.4ffbf51c6e347c0012607f525099d10e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27341: Altering max_length on sqlite: makemigrations creates correct migration, but migrate does not alter length of varchar in de database itself

[Django]

#27341: Altering max_length on sqlite: makemigrations creates correct migration,
but migrate does not alter length of varchar in de database itself
-+-
 Reporter:  Gerben Morsink   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Gerben Morsink):

 * 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: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.e54c1ccfa5c494d720264eb22893a19b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #27341: Altering max_length on sqlite: makemigrations creates correct migration, but migrate does not alter length of varchar in de database itself

[Django]

#27341: Altering max_length on sqlite: makemigrations creates correct migration,
but migrate does not alter length of varchar in de database itself
--+
 Reporter:  gabn88|  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.8
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  1 |  UI/UX:  0
--+
 I think the title is self-explanatory.

 At my local django installation, changing the max_length of a charfield
 did result in the correct migrations (a.k. 0010_autocreatedpy), but
 migrating the changes to the Sqlite database did not change the varchar in
 the database to the new max_length.

--
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/049.2027e16209a4f3ccfb64deb059536073%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.