this question also depends on the platform you are using - a noSQL DB such as google app engine that does not support joins would be slow to run 2 queries where you can use one....
i also use something like bruno's approach, setting readable and writable in the controllers as needed. On Wednesday, August 29, 2012 11:24:33 AM UTC-7, Alec Taylor wrote: > > I have been extending my auth_user table with a bunch of new options. > > When there's a 1:1 relation with the user, I'll store it in their profile. > > On 1:n, I'll keep them in separate tables. > > Now I am realising the problems with doing it this way. To make my > register form "nice" I have set almost all fields with readable=False and > writable=False. > > This means that I can no longer use the crud.create or crud.update form > creator helpers on those subset of a users' profile I want the form to > change for them. > > But it also has its advantage: no extra queries are required to grab all > the 1:1 fields of a users' profile after login. > > Is this enough of an advantage? > > Thanks for all suggestions, > > Alec Taylor > --
