Changes between Initial Version and Version 1 of Ticket #21896, comment 4


Ignore:
Timestamp:
Sep 28, 2014, 12:59:40 PM (10 years ago)
Author:
Ashish1206

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #21896, comment 4

    initial v1  
    22> We don't know what size the table might be in the future, so we have to raise this during ``makemigrations``; you might make the migration on a dev box with no entries and then run it on a production box with millions of rows, so it has to stay. Marking INVALID.
    33I am using django 1.7 and getting the same warning for fields when I use `makemigrations` on dev server.How to fix this?
     4
     5After deleting the privious models and again using makemigrations it works now.I don't know what happened!
    46 
Back to Top