(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, one client may have a list of products with just a few items of information, whereas another might have lots:- >>Customer 1 [Products] id description price attribute_z >>Customer 2 [Products] id description price attribute_a attribute_b attribute_c While it will be possible to normalize some of the information (id, description, price) it is not possible to normalize all of the attributes. It's not a case of some needing size / colour / etc attributes that could be put in other optional tables. These are completely internal items of information they need that will have no overlap with other organizations. I suppose I could have an 'products_additional' table along the lines of: customer_id attribute_name attribute_value I could then pivot the table to replicate the sort of table they need. However, I'm still going to have to have customer specific queries that join these tables up, because customer specific column names will come up. It all seems a bit messy. Maybe I just have to bite the bullet and get on with it, but I just wanted to know if this sort of thing happens a lot and if there is a better way of dealing with it. Regards ALJ _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
