> > 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?
> >
> The VPRO is handling million of objects, so i wouldn't worry about
> 30.000 objects.
> Maybe you would have to put indexes on some fields of your tables, in
> regard to fast searches.
Of course it's also a tradeof in terms of how managable your code will remain.
-how easy is it to query / update the answers,
-how wil you cope with users wanting to answer a question multiple times
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
if after that you also want to keep track of what user answerd what question your
object model already is to complex
question->posrel->possibleAnswer
| |
\____userrel________/
|
|
user
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 :)
I think that sometimes it's better to use node/xml fields
--
Kees Jongenburger
Mediapark C101 Hilversum
+31 (0)35 6772910
