Right you can used writable/readable = false so that you can only display fields you want user to update and from your server side you can update the other field as you want... If you want to show the other field later in other pages for example "Setting Pages" you can do so...
I did add more field on the table "auth_user" but remember it is good design to keep data consistent. On Feb 14, 10:16 pm, Panupat <panup...@gmail.com> wrote: > Thanks howsec. > > So if I want only a certain field to show up during registration, I > mark the ones I want to hide with writable/readable = False right? > Will doing so also prevent those field from editing later on? > > On Feb 15, 8:10 am, howesc <how...@umich.edu> wrote: > > > > > > > > > i think someone asked a similar question on this group recently, and there > > were some good opinions in that response thread if you can find it. > > > short answer (in my opinion): it depends on the database and your style. on > > GAE since you can't do joins i put all the info on the auth_user table. on > > mysql or postgres i tend to have a mixture that somewhat depends on the > > quantity of information. i also have grown to have no fear of adding > > columns to auth_user. > > > cfh
