let me think about this one.
On Aug 4, 7:41 pm, Richard <[email protected]> wrote:
> another issue I came across is that the deleted user can stay logged
> in with their previous session cookie. Is there an efficient way to
> get around this?
> Richard
>
> On Jul 19, 5:33 pm, Hans Donner <[email protected]> wrote:
>
> > Keep in mind if you reference to this user in other tables as well
> > (your apps). If you make joins against the user table this may lead to
> > unwanted results in your app.
>
> > If this is the case you perhaps only want to strip the roles and
> > permissions for this user.
>
> > But this is more related to your app internals than it is demanded by auth.
>
> > On Sun, Jul 19, 2009 at 07:28, mdipierro<[email protected]> wrote:
>
> > > It should be ok to just delete the user from the database. given the
> > > user id, you may also want to delete
>
> > > db(db.auth_group.role=='user_%s'%id).delete()
> > > db(db.auth_membership.user_id==id).delete()
>
> > > On Jul 18, 11:42 pm, Jason Brower <[email protected]> wrote:
> > >> What is the proper way to remove a user with the Auth method? I could
> > >> just delete them from the database. But I don't know about all the
> > >> connection they may have. Is there something built in to auth for this?
> > >> Perhaps it should be part of their edit profile page?
> > >> Best Regards,
> > >> Jason
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---
