#preferences data design

If you have a big application that requires a lot of settings and properties to be defined this is the generic design that you might want to look into. Here is some use cases for storing iPhone settings as an example:

USER_ID: '90392847'

PRODUCT_ID: 'IPHONE'

CATEGORY_NAME: 'SETTINGS'

PREFERENCE_NAME: 'GENERAL'

DETAIL_NAME: 'NETWORK'

ATTRIBUTE_NAME: 'ENABLE 3G' VALUE_TEXT: [Field name] 

ATTRIBUTE_NAME: 'VALUE' VALUE_TEXT: 'Y'

ATTRIBUTE_NAME: 'ATTRIBUTE STATE' VALUE_TEXT: 'REQUIRED'

ATTRIBUTE_NAME: 'OPERATOR' VALUE_TEXT: 'EQUALS'

--------------------------------------------------

USER_ID: '90392847'

PRODUCT_ID: 'IPHONE'

CATEGORY_NAME: 'SETTINGS'

PREFERENCE_NAME: 'GENERAL'

DETAIL_NAME: 'NETWORK'

ATTRIBUTE_NAME: 'CELLULAR DATA' VALUE_TEXT: [Field name] 

ATTRIBUTE_NAME: 'VALUE'          VALUE_TEXT: 'Y'

ATTRIBUTE_NAME: 'ATTRIBUTE STATE'    VALUE_TEXT: 'REQUIRED'