Yeah, thats a solution and the best one for a temporary ban (if a user uses strong language for example).
However, I prefer deleting it if, for example, a user abandons his account as the unsused accounts will just cram the database and make queries to the auth_user table slower than they need to be. Thanks for clearing this out for me btw. On May 19, 6:44 am, mdipierro <mdipie...@cs.depaul.edu> wrote: > Sorry. Not "blocked" but "disabled" > > On May 18, 4:59 pm, mdipierro <mdipie...@cs.depaul.edu> wrote: > > > > > We will add API to delete users and groups but it is safe to do it > > manually. > > > You can also block users by putting "blocked" in the user > > registration_key > > > On May 18, 4:35 pm, Magnitus <eric_vallee2...@yahoo.ca> wrote: > > > > I noticed that a special API via the instance of the Auth class is > > > provided to manage groups, user memberships to groups, permissions and > > > groups access to permissions. > > > > Is that purely a convenience thing or was it put in place to prevent > > > some weird crashes caused by race conditions if the DAL API is used > > > directly on the tables? > > > > An API is not provided to add/remove users (not in the manual > > > anyways). > > > > I see that there is an example where users is added directly with DAL > > > (page 134 of the pdf), but is it equally safe to detele users directly > > > with DAL? > > > > If so, should a special step (like blocking the user first) be taken?- > > > Hide quoted text - > > - Show quoted text -
