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 field should then be available in views for editing and reporting on data. Any standard approaches to this that don't require the user to manipulate the database and source code directly? Jaes --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
