#601 closed enhancement (fixed)
Unique_together documentation update
| Reported by: | Lllama | Owned by: | Jacob |
|---|---|---|---|
| Component: | Documentation | Version: | |
| Severity: | trivial | Keywords: | unique_together, unique |
| Cc: | Triage Stage: | Ready for checkin | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
The documentation for unique_together suggests that the constraint is only enforced at the admin site level when in fact it is enforced by the database as well (for PostgreSQL at least).
A quick update to the docs detailing this would aid new users.
Change History (3)
comment:1 by , 19 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:2 by , 19 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
The documentation now claims that it enforces at the DB level, but it doesn't appear to do so for mySQL.
comment:3 by , 19 years ago
| Resolution: | → fixed |
|---|---|
| Status: | reopened → closed |
constraint _does_ work at DB level for mySQL. Ignore previous. Appologies.
Note:
See TracTickets
for help on using tickets.
(In [822]) Fixed #601 -- Updated docs/model-api.txt unique_together section to say it's enforced at the database level.