Separating User from Profile I can understand, but using EAV for Profile seems like overkill to me. And it's not that difficult to update views/models to reflect a newly-added column, should it become necessary.
Actually, I can't see how using EAV would mean that updating view/models would be unnecessary. If they don't change, what's the point in adding new attributes? On Sun, Feb 8, 2009 at 8:30 AM, Andrea Cardinale <[email protected]> wrote: > > On Wed, Jan 28, 2009 at 8:37 PM, LunarDraco <[email protected]> wrote: >> Second, for my case I use an Entity Attribute Value EAV >> http://en.wikipedia.org/wiki/Entity-Attribute-Value_model table for my >> Profile fields, so that I can easily add additional profile fields >> without making structure changes or form/view changes. I simply add >> another field to my UserProfileProperty table. >> > > I read the wiki page and got an idea on how EAV is supposed to work > but I'd like to have more detailed on how to use it to model > User-Profile relationship. And what I'm not completely sure about is > that storing all profile data in an EAV table the value column must > have a type that can be used to store any kind of different values. > > Andrea > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" 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 -~----------~----~----~----~------~----~------~--~---
