I am doing an application like Form builder in Cakephp.
I’ve created the module for Designing the forms. Is it a good way to create a separate table for each forms in the case of form building?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am doing an application like Form builder in Cakephp.
I’ve created the module for Designing the forms. Is it a good way to create a separate table for each forms in the case of form building?
I don’t think so. The database design should come first and it should be a clean, simple and as efficient as possible. Then you build your forms.
A good form building app should be able to look at a database table, or a group of tables, and figure out what belongs where, what type of content is being stored (Ints, primary keys, text, blobs, URLs) and function with as little configuration from the end user as possible. Otherwise you’re not going to be able to normalize your database, and you’re going to have all kinds of data all over the place.
It’s easy enough to get the info on a particular table. That’s the best route I think.