What you are saying is you are holding information about items which have
different characteristics. To represent these as relations you would have a
product entity then you would have an attribute entity that would be like
(product_id,attribute_id,attribute_name,attribute_value) eg:
screwdriver1210, 1, handle, wood
screwdriver1210, 2, point, crossdrive
screwdriver1210, 3, weight, 180
hammer0899, 1,weight, 3.35
hammer0899, 2 head, steel
etc
You then join from product to this table and pick up the listed features.
You can of course use attribute_ids that are standardised eg 56 is always
weight etc
That's one way. Alternatively if there aren't too many different attributes
you can collapse ('denormalise') these into a bunch of fields in the product
table. I would recommend leaving your model normalised until you are forced
to compromise.
--
View this message in context:
http://old.nabble.com/How-to-deal-with-non-%27normilize-able%27-tables-tp26495733p26516107.html
Sent from the SQLite mailing list archive at Nabble.com.
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
