Opened 9 years ago

Closed 9 years ago

Last modified 7 years ago

#451 closed defect (invalid)

There should be OneToManyField support

Reported by: leo@… Owned by: adrian
Component: Database layer (models, ORM) Version: 1.1
Severity: normal Keywords: Field
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:


We can use OneToOne, ManyToOne, ManyToMany, it will be nicer if we can use OneToMany.

Attachments (0)

Change History (5)

comment:1 Changed 9 years ago by Stan Seibert <volsung@…>

Isn't this implied by the use of ForeignKey() on the "many" side?

comment:2 Changed 9 years ago by adrian

  • Resolution set to invalid
  • Status changed from new to closed

OneToMany is redundant. See ForeignKey, as Stan Seibert said above.

comment:3 Changed 9 years ago by anonymous

  • Resolution invalid deleted
  • Status changed from closed to reopened

I don't think ForeignKey is enough here. Here you are an example: I get two objects both have OneToMany relationship with another thrid object. How could i declare all these three classes?

comment:4 Changed 9 years ago by hugo <gb@…>

  • Resolution set to invalid
  • Status changed from reopened to closed

You would just put in two ForeignKey relations into the third class that point back to the first two classes. But stuff like this should be discussed on the IRC channel or in the mailing list, not in the bugtracking system.

comment:5 Changed 7 years ago by anonymous

  • milestone Version 1.0 deleted

Milestone Version 1.0 deleted

Add Comment

Modify Ticket

Change Properties
<Author field>
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.