What is the best strategy for allowing application users to define
database fields on the fly?
For example in a customer database you would have customer name,
address and address. One company might want to include some grouping
fields so they add a User Defined Field called CustomerType. This
You need an additional table with user fileds: id, user_id, fieldname,
fieldvalue. User hasMany UserDefinedFields.
On Dec 7, 4:17 pm, JTTACJ1 [EMAIL PROTECTED] wrote:
What is the best strategy for allowing application users to define
database fields on the fly?
For example in a customer
