One Into Many
From CSSEMediaWiki
(Difference between revisions)
(New page: I encountered this during my design study. --~~~~ == Overview == This pattern is to be used in cases where a previous implementation has a one to one relationship and it needs to be modif...) |
|||
| Line 1: | Line 1: | ||
| − | I encountered this during my design study. --[[User:Matthew Harward|Matthew Harward]] 00:57, 7 August 2009 (UTC) | + | I encountered this during my design study and thought it would make a worthy addition to the currently empty set of amelioration patterns. --[[User:Matthew Harward|Matthew Harward]] 00:57, 7 August 2009 (UTC) |
== Overview == | == Overview == | ||
| Line 5: | Line 5: | ||
== The Problem == | == The Problem == | ||
| − | During initial coding/design, you failed to notice that a relationship had the potential to be one-to-many and instead coded it as one-to-one. Now, you realise your problem and need to | + | During initial coding/design, you failed to notice that a relationship had the potential to be one-to-many and instead coded it as one-to-one. Now, you realise your problem and need to rectify it. |
== General Issues == | == General Issues == | ||
Revision as of 03:27, 7 August 2009
I encountered this during my design study and thought it would make a worthy addition to the currently empty set of amelioration patterns. --Matthew Harward 00:57, 7 August 2009 (UTC)
Contents |
Overview
This pattern is to be used in cases where a previous implementation has a one to one relationship and it needs to be modified to a one to many relationship. This pattern is specifically designed for Objects; however it may be used for lower or higher level concepts.
The Problem
During initial coding/design, you failed to notice that a relationship had the potential to be one-to-many and instead coded it as one-to-one. Now, you realise your problem and need to rectify it.
