I am designing a database structure for a simple solution, and am being suggested to change my existing layout. I have argued my layout is "cleaner" but being told I have needless tables...
Say I have a product table. I also need to store long text fields of description and internal_review.
My way involves a main product table, with a table each for description and internal_review, both joining against a common product_id field.
The way being suggested is as above, but with a single product_texts table, with a field for description and a field for internal_review, again joining on product_id.
Does anyone have any feelings either way on this?
I think I just like the clean separation, but can see benefit in the suggested way as far as efficiency goes...
Question
+Dick Montage Subscriber²
I am designing a database structure for a simple solution, and am being suggested to change my existing layout. I have argued my layout is "cleaner" but being told I have needless tables...
Say I have a product table. I also need to store long text fields of description and internal_review.
My way involves a main product table, with a table each for description and internal_review, both joining against a common product_id field.
The way being suggested is as above, but with a single product_texts table, with a field for description and a field for internal_review, again joining on product_id.
Does anyone have any feelings either way on this?
I think I just like the clean separation, but can see benefit in the suggested way as far as efficiency goes...
Link to comment
Share on other sites
20 answers to this question
Recommended Posts