I didn't supposed it to be in auth. I just thought it could be made like the auth's permission table just in lock's table... :) Anyway I don't mind the background :-o it should just work :)
On márc. 25, 20:51, mdipierro <mdipie...@cs.depaul.edu> wrote: > This is done in kpax to prevent two users from editing the same wiki > page at the same time. It involves ajax keepalive. For efficiency the > locking time is stored in the same table being locked. I am not sure > this belongs to auth but we could have a plugin. > > Massimo > > On Mar 25, 2:16 pm, szimszon <szims...@gmail.com> wrote: > > > > > Hello! > > > I would like to have a built in support for database locking. > > > I think about something like auth_permission... > > I can make an entry in it with user_id, name > > (create,read,update,delete,select), table_name, record, > > expiration_time, type(soft,hard)... > > > soft type - other user could override it with an additional popup or > > whatever (like deleting question)... > > > And crud could use it out of the box :-D -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web...@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.
