LeonS wrote:
Thats right, because every User has the same profile fields , the
possible Profile fields are saved in the Profile model.
The value of a profile field of one user is saved in the Profileship
model in the field value.
So how can i put that in a view based on the Profilegroup?
So, for example there are profile field for work, main profile fields,
contact field (msn, email, adress) and so.
So i think there is usage for the user.
On 12 Jan., 17:50, Marnen Laibow-Koser li...@ruby-forum.com wrote:
LeonS wrote:
Thats right, because every User has the same profile
LeonS wrote:
So, for example there are profile field for work, main profile fields,
contact field (msn, email, adress) and so
These could all be in the User model or, failing that, in a separate
Profile model where User has_one :profile. Why do you need Profileship
and ProfileGroup?
So
Let me explain Why i Write the Models:
i'm Coming from Database Development, so normalization is very
Important for me.
If i create just a Profile Model and put all possible profile Fields
into that, than there is no normalization
Should i avoid the normalization in Case of RoR and keep the Models
LeonS wrote:
Let me explain Why i Write the Models:
i'm Coming from Database Development, so normalization is very
Important for me.
To me too.
If i create just a Profile Model and put all possible profile Fields
into that, than there is no normalization
Of course there is. Won't every
5 matches
Mail list logo
