Changes between Initial Version and Version 1 of Ticket #12751, comment 5


Ignore:
Timestamp:
06/23/2013 03:14:14 PM (7 years ago)
Author:
Cal Leeming
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #12751, comment 5

    initial v1  
    1 Inadvertently I was reproduce this in Django 1.5 whilst attempting to migrate data between two projects. It was the same thing, unexpected NULL columns caused select_related() to return an empty queryset. However, at least in my case, I was able to fix this problem by doing a complete re-import of my data into a clean syncdb. The problem seems to happen after you make manual modifications to the table schema and you get something wrong. Although it would be nice to have some sort of warning for this, someone will have to take time/effort to provide a small project which can reproduce this problem.
     1Inadvertently I was able to reproduce this in Django 1.5 whilst attempting to migrate data between two projects. It was the same thing, unexpected NULL columns caused select_related() to return an empty queryset. However, at least in my case, I was able to fix this problem by doing a complete re-import of my data into a clean syncdb. The problem seems to happen after you make manual modifications to the table schema and you get something wrong. Although it would be nice to have some sort of warning for this, someone will have to take time/effort to provide a small project which can reproduce this problem.
    22
    33I'm going to re-mark as open on the basis that I was able to reproduce.
Back to Top