I've done this with the latter approach. I made a person model that had more person-specific information and made the user field a foreign key and added the edit_inline option to have the information right there in the user interface:
user = meta.ForeignKey(auth.User, edit_inline=meta.STACKED, num_in_admin=1, max_num_in_admin=1) This works pretty well for me at least. -berto. On 1/30/06, char <[EMAIL PROTECTED]> wrote: > > I've seen a couple of approaches on this mailing list for adding > application specific fields to the User class. The first involves > extending auth.User but this seems a little complex, and was > specifically labeled an "advanced" method. It doesn't seem like you > should have to break out deep black magic to do something so standard. > > The other method is to have a foreign key pointing to a User. This is > easier but it makes for a messy Admin interface (resulting in both a > User class and a separate MyUser class that needs to be associated with > a User). What is the "canonical" way for extending atuh.User with > application specific fields? > >
