Changes between Initial Version and Version 4 of Ticket #22424


Ignore:
Timestamp:
May 5, 2014, 12:32:04 PM (10 years ago)
Author:
loic84
Comment:

Fixed the name of the commands in the ticket description.

I originally assumed this was an issue before the migrate step, but it's indeed an SQL issue due to one-off defaults, Django uses db defaults for these.

The fix for MySQL is to not provide a default for BLOB/TEXT in the SchemaEditor. Although we'll now need to propagate the default value manually.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #22424

    • Property Triage Stage Unreviewed → Accepted

  • Ticket #22424 – Description

    initial v4  
    1010}}}
    1111
    12 When I type "python manage.py migrate" I am asked to enter default value.
    13 But BLOB/TEXT columns can't have a default value and if i will type something like 'blabla' then after command "python manage.py makemigrations" i will see error. I think it is bug :)
     12When I type "python manage.py makemigrations" I am asked to enter default value.
     13But BLOB/TEXT columns can't have a default value and if i will type something like 'blabla' then after command "python manage.py migrate" i will see error. I think it is bug :)
Back to Top