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


Ignore:
Timestamp:
Sep 25, 2022, 2:39:43 AM (2 years ago)
Author:
Bishal Gautam

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #34050, comment 2

    initial v1  
    1 Yes, as an experiment, I changed the name of constraint by putting `*` in the file name. Django created the file name with the exact name of the constraint but failed to create a migration file because of invalid name of file. I have also added an attachment for this. Kindly find above.
     1Yes, as an experiment, I changed the name of constraint by putting `*` in the constraint name. Django created migration file name with the exact name of the constraint but failed to create a migration file because of invalid name of the file. I have also added an attachment for this. Kindly find above.
    22
    33- This didnot create a migration file and generated a error from django core. I think it still tells the user that the invalid file name causes this issue.
Back to Top