Opened 9 years ago
Closed 9 years ago
#24821 closed Bug (invalid)
makemigrations generates long files names
| Reported by: | Jean Marcos da Rosa | Owned by: | nobody |
|---|---|---|---|
| Component: | Migrations | Version: | 1.8 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
I think it is a bug, it's my first report, so sorry if missing information or accuracy.
Command makemigrations created a migration file with the very long name: "0002_dfeambiente_dfeambientecont_dfearquivocompactado_dfearquivoinfo_dfecancelamento_dfecertificado_dfecl.py"
This occurred when running makemigrations after major changes in my models.py
Change History (2)
comment:1 by , 9 years ago
comment:2 by , 9 years ago
| Component: | Uncategorized → Migrations |
|---|---|
| Resolution: | → invalid |
| Status: | new → closed |
| Summary: | migration file very long name → makemigrations generates long files names |
Note:
See TracTickets
for help on using tickets.
There's no harm in renaming the file to choose your own shorter name or using the makemigrations --name option. If you made a lot of changes at once, it makes sense that the auto-generated name would be long. I don't think it's a bug.