Reply to thread

Message: <blockquote data-quote="Raven" data-source="post: 1410437" data-attributes="member: 558368">OK, now the part of every database that scares the hell out of me - the archtecture. How do we plan on doing this?[CODE]Product- id- name- info- priceReviews- id- product id (Points to product ID so we know what it's a review of)- review- reviewerPics- id- product id[/CODE]Or something more complex?[CODE]Product- id- manufacturer [link: Manufacturer.id]- model- street price- power input/output- T/S spec (where applicable)- Efficiency (where applicable)- author id [link: author.id]- type id [link: type.id]Type- id- kind {subwoofer, amp, comp set, coax, mid, tweeter, enclosure, etc}Reviews- id- item reviewed (product, manufacturer, other review, author, or picture)- item type (review brand X subs in general, or brand Y comps in general! if applicable)- item id [link: item reviewed.item id] (if applicable)- date posted- review- author id [link: author.id]pictures- id- item reviewed (product, manufacturer, other review, author, or picture)- item id [link: item reviewed.item id]- picture- author id [link: author.id] Authors- id- username- join date- posts[/CODE](It is said a good programmer looks both ways before crossing a one way street.)Either way can be done, but we need this figured out before we can get to the all important part of putting data into and getting data out of it.</blockquote>

Top