Mark Sargent wrote:
> Hi All,
> I have the job of creating a DB for an online clothing company. I have
> some experience with relational design and sql and php. I'm stumped as
> they have products that contain numerous attributes, and are wishing to
> get away, if possible, with entering separate records for each and every
> product that has different ones. I will list below some example products
> and their attributes.
> below is a link to what they have on Ebay at the moment,
> keep in mind, I have only listed attributes above, not the actual table
> designs. They deal with a lot of variety within brands etc. Anyone got
> any solutions for this? I haven't started on a basic design yet, but am
> looking to do that soon. I f i can minimize their record input, that'd
> be great Cheers.
My solution would be 3 Databases where one has ID,Attrib_object_id,
And the other two would be an attrib database and an object databse.
Yep, something like that.
Smileys rule (cX.x)C --o(^_^o)
Dance for me! ^(^_^)o (o^_^)o o(^_^)^ o(^_^o)