Opened 9 years ago
Closed 9 years ago
#26453 closed Cleanup/optimization (wontfix)
SITE_ID should start from 1, not 0
| Reported by: | Yaroslav Nikitenko | Owned by: | nobody |
|---|---|---|---|
| Component: | Documentation | Version: | 1.8 |
| Severity: | Normal | Keywords: | SITE_ID, sites |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | yes | UI/UX: | no |
Description
I had a problem with migrations when I set SITE_ID to 0.
In the documentation I read that it should be integer, so I thought 0 would be fine.
I had the following error:
ValueError: The database backend does not accept 0 as a value for AutoField.
I suggest writing in the documentation that it should start from 1. The same problem is in the documentation for django 1.9.
Change History (1)
comment:1 by , 9 years ago
| Easy pickings: | set |
|---|---|
| Resolution: | → wontfix |
| Status: | new → closed |
| Type: | Bug → Cleanup/optimization |
Note:
See TracTickets
for help on using tickets.
Thanks for the suggestion. This restriction only applies to MySQL, however, and I don't think it's a big enough pitfall to warrant a note in the docs.