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.
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:
(Sorry to target this at sqlite users, as this is a general db
problem, but if anyone could point me in the right direction...)
I have a database that is well structured, but various clients have
different information they need which means some info won't fit into a
standard table.
For example,
3 matches
Mail list logo
