Opened 9 years ago
Closed 9 years ago
#25642 closed Bug (worksforme)
creating a model named "order" cause sqlite database to crash
| Reported by: | Jérôme Hugon | Owned by: | nobody |
|---|---|---|---|
| Component: | Migrations | Version: | 1.8 |
| Severity: | Normal | Keywords: | sqlite |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Well,
I wanted to order my things with a custom order, so I created a "order" model in my class.
And bam, sqlite didn't accept it, and all went bad.
Because order is a keyword on sqlite, and cannot be accepted
Change History (2)
comment:1 by , 9 years ago
comment:2 by , 9 years ago
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
I didn't have any trouble running makemigrations and migrate for a model named 'order' and 'Order'. In fact, Django's test suite has several models named "Order". Can you be more specific about the steps to reproduce and the exception that you ran into?
Note:
See TracTickets
for help on using tickets.
Really not a bad bug, but I think would be easy to throw an exception and tell the user that it is code breaking