I think the best pratice is a different table, then you make a reference
between tables using the user_id.
It is easy with DAL because you can do traversing, for example
db.define_table('userinfo',Field('user_id',db.auth_user,requires=IS_IN_DB(...)),Field('....'),Field('...'))
userlist = db(db.userinfo.user_id==foo).select().first()
name = userlist.user_id.first_name
email = userlist.user_id.email
...
You need to query just the second table to get the data on the first one,
and you dont need to redefine the auth_user model.
Bruno Rocha
http://about.me/rochacbruno/bio
2011/1/20 scausten <[email protected]>
> I've got a few items of supplementary data about my users relating to
> my e-commerce app, including current balance, total earnings, and
> other bits and pieces. Because these are not directly related to
> access control, I have a gut feeling that I should store them in a
> different table and have a single reference from auth_user to these
> miscellaneous data.
>
> What are people's thoughts on best practice for this?
