The best way is to customize the auth_user table as shown in the
slides, insdead of subclassing it. Else it is much more complex than
just setting auth.settings.table_user, since references from other
built-in tables will break
Massimo
On Jun 9, 10:42 am, Trollkarlen <robbelibob...@gmail.com> wrote:
> Fran wrote:
> > On Jun 9, 11:42 am, Robert Marklund <robbelibob...@gmail.com> wrote:
> > > Cant auth be changed somhow to it will be easier to extend like this:
> > > db.define_table('auth_user2',
> > > db.auth_user,
> > > SQLField('nickname'),
> > > SQLField('image','upload'))
> > > The problem to day is the:
> > > table.email.requires = [IS_EMAIL(), IS_NOT_IN_DB(db, '%s.email'
> > > % self.settings.table_user._tablename)]
> > > It will check the auth_user table instead of my extended table for the
> > > email
> > > to be uniq.
>
> > Try:
> > auth.settings.table_user_name = 'auth_user2'
>
> > F
>
> Do i need to set that before calling the auth.define_tables() ?
> And is it the same with auth.settings.table_user ?
>
> /T
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"web2py Web Framework" group.
To post to this group, send email to web2py@googlegroups.com
To unsubscribe from this group, send email to
web2py+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---
