Remove UserTeam from the model

Bug #722965 reported by David Coles
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MUGLE
Fix Released
High
Prageeth Silva

Bug Description

UserTeam should not be part of the JDO model. This table should should only need to be instantiated at the database layer (ideally automatically by JDO) to implement a many-to-many relationship between User and Team objects.

David Coles (dcoles)
Changed in mugle:
status: New → Confirmed
importance: Undecided → High
status: Confirmed → Triaged
Changed in mugle:
status: Triaged → Fix Committed
Revision history for this message
Matt Giuca (mgiuca) wrote :

But it isn't sufficient to simply remove the class. Now there is no association between User and DevTeam. They both need to have a set of the other (a many-to-many relationship).

Changed in mugle:
status: Fix Committed → Triaged
Revision history for this message
Prageeth Silva (prageethsilva) wrote :

This was not realised at the time. However, the mapping of relationships (one-to-one, one-to-many and many-to-many) is being done; that will be the next commit.

Revision history for this message
Prageeth Silva (prageethsilva) wrote :

The fixed version has been committed (revision 33).

Changed in mugle:
status: Triaged → Fix Committed
David Coles (dcoles)
Changed in mugle:
milestone: none → 0.1.1
Matt Giuca (mgiuca)
Changed in mugle:
assignee: nobody → Prageeth Silva (prageethsilva)
Matt Giuca (mgiuca)
tags: added: datastore
removed: database
Matt Giuca (mgiuca)
Changed in mugle:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.