tag:robotlegs.tenderapp.com,2009-10-18:/discussions/problems/302-to-single-model-class-or-moreRobotlegs: Discussion 2018-10-18T16:35:25Ztag:robotlegs.tenderapp.com,2009-10-18:Comment/67674512011-04-21T10:07:33Z2011-04-21T10:07:33ZTo single model class or more?<div><p>Certainly not a single model.<br>
There's not a clear-cut answer to your question, it all depends on
the data, the relation between the types of data and what you need
to do with it.<br>
In general though there's not necessarily a 1-to-1 relationship
between your VO's and your models. Meaning that data from one VO
can go to different models, or a model can receive data (through a
command, of course) from various VO's.</p></div>creynderstag:robotlegs.tenderapp.com,2009-10-18:Comment/67674512011-04-21T23:32:53Z2011-04-21T23:32:55ZTo single model class or more?<div><p>I through over the examples in RL, It's seems all design in
(1(model) to more(VO))</p>
<p>M depends on the data.<br>
V<br>
C<br>
S<br>
aha, this 'questionVO' is not relate to RL, but on the data, as you
sad ,since I lost the basic principle.</p>
<p>Thanks RL<br>
Thanks creynders.</p></div>Alantag:robotlegs.tenderapp.com,2009-10-18:Comment/67674512011-04-21T23:43:37Z2011-04-21T23:43:37ZTo single model class or more?<div><p>Now. dropTextVO,reportVO,queueVO I through commands in event
dispatch<br>
and three model<br>
settingModel(a db table)<br>
CommentModel(a db table)<br>
UserModel(a db table)</p></div>Alan