Note: To post to a thread, you must be logged in.
Hi Friends - I'd appreciate your expert thoughts and suggestions for the below requirement. We dont have a static entity model i.e. our table doesn't contain a fixed set of coulmns. Or to put in another way we doesnt want our CUSTOMER entity to contain just id, firstName, lastName and age. We want our entity to be generic (name=value pair) so that we can accomodate N number of attributes without touching the TABLE def. This gives us lot of flexibility while boarding new customers etc. As of now our CUSTOMER table has around 200 attributes (and increasing).
How are these kind of things modeled if we use RDBMS in the backend?
Thank you in advance!