i'm working with data that requires revisions.
the easiest way to think about it is a product by
revision. for example,
product A, rev 1
product A, rev 2
product A, rev 3
where is revision is potentially a viable product to
some customer. iow, customer blue may order product
A, rev 3 and customer green may want product A, rev 1.
i have put some thought into this and developed the
following scheme...
three tables (T=table, C=column in table, PK=primary
key, FK=foreign key):
T product_base
C PK product_base_id
C product_number
C product_name
C product_description
T revision
C PK revision_id
C revision_number
C revision_description
T product_revision
C PK product_revision_id
C FK product_base_id
C FK revision_id
does this seem like a reasonable approach to solving
this problem? please let me know if you have a better
approach or more information to improve this approach.
__________________________________
Do you Yahoo!?
Yahoo! Mail - 250MB free storage. Do more. Manage less.
http://info.mail.yahoo.com/mail_250