Enjoy an ad free experience by logging in. Not a member yet? Register.
Results 1 to 1 of 1
03-23-2004, 04:21 PM #1
- Join Date
- Jul 2002
- Thanked 0 Times in 0 Posts
Dynamic Tables, is it a good design??
I'm about to write an app where my client wants full access creating his own presentational tables. We have some products and for each product there are some factors that should be demonstrated, like their weights, portability, battery type and ... The problem is we don't know what factors are necessary for each product. So, for a new product you might have some fields (instead of "factors" I'd rather use this term) but for another product you don't have those fields. And then for each fied my client should be able to define some sub fields. Let's say if product A (which is a MP3 Player) has a field called "Audio", then this field has some sub fields like "No. of Channels", "Frequency Range", "Line out level", "S/N Ratio" and ... . All the fields and sub fields are dynamic, which means we have no idea what they are and my client should be able to create/edit/delete them. Oh my God! This is like phpMyAdmin, huh?!
This is basically a 3 level table design. This is the first table:
MainFieldAutuNumID ProductId MainFieldName
SubFieldAutuNumID MainFieldAutuNumID SubFieldName
I think the first design (not using dynamic tables) is easier to implement, but then I was criticizing myself that hey, if you ever wanted to write something like Windows, I mean an operating system, that everything should be dynamic, then what did you do?
What is your idea? Do you think that it's better I do it the first way, or the 2nd? And why?