At the database level I was wondering myself if I will not use the initials
as PK... It's not clear to me how I will manage the authentification. Some
person ask for double authentification (LDAP - active directory) and an
authentification for data creation. The database should be as decoupled as
possible from web2py, since I would have to validated the conformity of
database schema. The database will be used with others tools, so all the
constrains have to be implemented at database level.
If you have any Idea, I will take it.
I saw you made a couple of web2py slice...
I might need your help.
Jonhy
2010/6/8 mr.freeze <nat...@freezable.com>
> I think it would be more useful to record the auth user id instead
> since you wouldn't be able to find the corresponding user record from
> the initials.
>
> On Jun 8, 5:29 pm, Jean Guy <jean...@gmail.com> wrote:
> > Could it be a good practice to implement electronic signature of the
> > database records like this :
> >
> > db.define_table('atable',
> > SQLField('var1'),
> > SQLField('var2',default=db(db.auth_user.id
> > ==auth.user_id).select(db.auth_user.initials).first().initials))
> >
> > It needs that the user be authentified otherwise the app won't work, but
> as
> > long as the user as to be authentified for doing accessing the database,
> it
> > should be ok...
> >
> > What do you think?
> >
> > My goal is to have each records signed (stamped with users initials
> > actually) at the database level.
> >
> > Thanks.
> >
> > Jonhy
>
