#10981 closed (fixed)
Notes about using string for relationship target model name slightly unclear
| Reported by: | Ramiro Morales | Owned by: | Jacob |
|---|---|---|---|
| Component: | Documentation | Version: | dev |
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Accepted | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
The section that describes usage of string of ForeingKeys (and that is linked from the ManyToManyField and OneToOneField sections when describing similar features) isn't completely clear about if the 'other_app.model_name' notation is supported or not. Attached patch tries to solve this and adds a description of the supported scenario with an example, also marking it with 'versionchanged:: 1.0'.
Found while trying to understand #10405, see django-dev thread: http://groups.google.com/group/django-developers/browse_frm/thread/3c38afb3355ecda6/2e533858fd1a64c6?hl=en&tvc=1#2e533858fd1a64c6
Attachments (2)
Change History (9)
comment:1 by , 17 years ago
| Has patch: | set |
|---|
by , 17 years ago
| Attachment: | 10981-string_model_names_notes.diff added |
|---|
by , 17 years ago
| Attachment: | 10981-string_model_names_notes.2.diff added |
|---|
comment:2 by , 17 years ago
| milestone: | → 1.1 |
|---|---|
| Owner: | changed from to |
Moving to list of documentation tickets to be considered for 1.1
comment:3 by , 17 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:4 by , 17 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|
comment:5 by , 16 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
comment:6 by , 16 years ago
Note:
See TracTickets
for help on using tickets.
New corrected and sllightly enhanced iteration