Many thanks for all the options! Since I'm on the subject of large forms, I was wondering what you opinion of appropriate class / db design is for such cases (300+ fields)? I was thinking of splitting the form into a number of sub-forms each with its own entity / table. The main issue with this would be doing lots of db joins - especially considering that the fields to sub-form ratio would vary (some could have up to 30 fields and others as little as one). There's also the EAV approach but there seem to be many conflicting opinions on this. I'm currently using a relational db but a move to nosql would be possible if it would greatly simplify this issue...
CN -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Large-forms-tp4669718p4669748.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
