Tahnks for the reply. It's really interesting to read through it and I
think I have a pretty clear idea now of the purpose of EAV and of
which are the context in which is worth to aplly it.
I'm looking forward for your user-profile plugin;)
On 2/16/09, LunarDraco wrote:
>
> I use EAV because I h
I use EAV because I have multiple clients using the same user/profile
code. Each client wants a different list of profile fields. I found
myself rewritting the same code slightly different each time. It was
time to automate some of that process.
I have two models Profile and ProfileFields. The Pro
On Sun, Feb 8, 2009 at 6:49 PM, brian wrote:
>
> 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
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 unn
On Wed, Jan 28, 2009 at 8:37 PM, LunarDraco 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/vie
I split my tables/models into logical objects ...
User:
An account to login to a site (id, user_group_id, username, email,
password etc.)
User Group:
Groups of users which can be applied access rights (id, name)
Person:
An actual person (id, user_id, first_name, last_name, full_name, dob,
gende
: January-28-09 7:07 PM
To: CakePHP
Subject: Re: Separating user and profile tables
LunarDraco, thanks for the explanation! Now it's clear why Janne wants to
separate the information.
--~--~-~--~~~---~--~~
You received this message because you are subscrib
LunarDraco, thanks for the explanation! Now it's clear why Janne wants
to separate the information.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to cake-php@google
> Why do you want to separate login information from other information
> about the user?
> I cant't think of a good reason to do this.
One good reason is you want to support multiple login protocols like
OpenID or your own internal.
You need to be able to store your sites profile Info and associat
Thanks Dave Maharaj, works like a charm.
On Jan 28, 8:46 am, Braindead wrote:
> Why do you want to separate login information from other information
> about the user?
> I cant't think of a good reason to do this.
>
> Markus
If you think system like facebook, you probably understand what I
mean.
Why do you want to separate login information from other information
about the user?
I cant't think of a good reason to do this.
Markus
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this
input('Profile.firstname');
echo $form->input('Profile.lastname');
echo $form->input('User.username');
echo $form->input('User.password');
echo $form->input(
Hi,
I´m doing a pretty simple test project with Cake and having some
serious problems. I think the solution may be really simple, but I
just cant solve it by myself.
What I want is simple one-to-one relation between user and profile
tables. When user registers to system, his/hers username and pa
13 matches
Mail list logo
