> > > This puts a lot of pressure on the posrel and insrel tables, > > > which are also used in a lot of other relations. Will MMBase > > > perform sufficiently under these conditions? Does anyone have > > > experience with very large clouds and MMBase performance? > > > > > For me my "golden" rule is that content that might be reused > must be in a "real" object You have the same kind of problem > when you try to make multiple choice question-answer it > doens't make much sence to create separate question and an > answer object (or do you want to create a question and create > a posrel to a "searched yes" object; the answer "yes" doesnt > mean anything on it's own
Seems like a very sensible rule, thanks. I think that reuse of answer options (yes, no, male, female, etc.) is useful if you have several forms with similar questions. Separating answer options from questions gives you a more generic cloud model. > after all you might even want to store the questions in the > answer object. since a user answers a specific question his > answer might get wrong when you edit the original question :) Our intent is to make forms immutable once published. Changing the order of questions for example would make managing the answers a lot more difficult. > > I think that sometimes it's better to use node/xml fields What do you mean by node/xml fields? Fields with structured content? Ronald Wildenberg Kennisnet
