Hi CityDev,
Thanks for getting back to me on this and sorry for not getting back
before. I thought it had dropped off the bottom of the forum.
Yeah ... it's a pain in the backside. I'd prefer to keep everything
normalised, but as I said, it isn't going to be possible. Thanks for
the suggestions.
I'm a bit miffed because I'm of all the additional queries I'll have
to write on the fly to query these quirky tables. Nevermind.
ALJ
On Nov 25, 5:44 pm, CityDev <nab...@recitel.net> wrote:
> 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-table...
> Sent from the SQLite mailing list archive at Nabble.com.
>
> _______________________________________________
> sqlite-users mailing list
> sqlite-us...@sqlite.orghttp://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
