Results 1 to 2 of 2
  1. #1
    Join Date
    Mar 2004

    Question Unanswered: Dynamic structure of a table?!!

    Hi all,
    I have an ER diagram which has an entity called "Form" .This is a typical electronic Form but number of its fields are not known and may vary at future.
    What is the best logical design for this case? If I create a table for this Form I should add columns to it in the future.This does not seem nice.Also I do not want to use "Entity-Attribute-Value" method as described at:


  2. #2
    Join Date
    Sep 2002
    Provided Answers: 1
    Why are you modelling generic "forms"? This is meta-data modelling really, so something like EAV may actually be appropriate - assuming there is a need to model arbitrary "forms" at all.

    For example, if I wanted to create a database to document all my Oracle "Forms Builder" forms then I would use tables like:

    create table forms (form_name, ...)
    create table blocks (form_name, block_name, block_seq, ...)
    create table items (form_name, block_name, item_name, item_seq, ...)

    However, normally one designs a database to reflect the underlying data (employees, departments, orders), not the forms (employee new hire form, order form).

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts