Changes between Initial Version and Version 1 of Ticket #26171, comment 2


Ignore:
Timestamp:
Feb 5, 2016, 2:35:55 AM (8 years ago)
Author:
Walter Doekes

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #26171, comment 2

    initial v1  
    11Interestingly we've run into a bug caused on the same spot.
    22
    3 We run a test case that check whether there are any unmigrated apps. In both the non-DB (SimpleTestCase) and SQLite-DB driven and REUSE_DB test it succeeds, but in the (newly created) InnoDB case, it claims that a lot of foreign key indexes are missing exactly because of this InnoDB exception.
     3We run a test case that checks whether there are any unmigrated apps. In the (a) non-DB (SimpleTestCase) and (b) SQLite-DB driven and (c) REUSE_DB test it succeeds, but in the (d) (newly created) InnoDB case, it claims that a lot of foreign key indexes are missing exactly because of this InnoDB exception.
    44
    5 I wonder why that check is there. Removing the `db_index=False` did not seem to have any negative impact, and it causes the weird behaviour to go away.
     5I wonder why that check is there. Removing the `db_index=False` did not seem to have any negative impact, and it causes the unexpected behaviour to go away.
    66
    77----
Back to Top