Why would 1.000 subforms in a db be a bad idea?

Posted by KlaymenDK on Stack Overflow See other posts from Stack Overflow or by KlaymenDK
Published on 2010-06-17T16:16:28Z Indexed on 2010/06/17 16:23 UTC
Read the original article Hit count: 175

Filed under:
|

Warm-up

I'm trying to come up with a good way to implement customized document forms.

It's for a tool to request access to applications; each application will want to ask its own specific questions. The thing is, we have one kind of (common) user who needs to fill in and submit documents based on templates, and another kind of (super) user who needs to be able to define what each template needs to contain.

One implementation option would be to use a form (with the basic mandatory stuff), and have that form dynamically include a subform appropriate to the specific task at hand. The gist of the matter is that we could (=will!) quite easily end up having many hundreds of different subforms!

(NB. These subforms will be maintained in an automated manner, but that is another topic that may be considered outside the scope of this Question.)

Question

It's common knowledge that having a lot of views in a Notes database is Bad Thing. But has anyone tried pushing the number of forms or subforms and made any experiences regarding performance?

© Stack Overflow or respective owner

Related posts about Performance

Related posts about lotus-notes