Comments on: Disabling users instead of deleting. http://www.splee.co.uk/2006/09/07/disabling-users-instead-of-deleting/ Bring out the g33k Thu, 20 Nov 2008 12:37:45 +0000 http://wordpress.org/?v=2.6 By: Splee http://www.splee.co.uk/2006/09/07/disabling-users-instead-of-deleting/#comment-7109 Splee Mon, 11 Sep 2006 13:28:54 +0000 http://www.splee.co.uk/2006/09/07/disabling-users-instead-of-deleting/#comment-7109 That works fine as long as there\'s no encryption algorithm set in your `app.cfg`. As soon as you decide you want to store passwords in a more secure manner your method of disabling the user is non-reversable and not the desired behaviour for this scenario in particular. That works fine as long as there\’s no encryption algorithm set in your app.cfg. As soon as you decide you want to store passwords in a more secure manner your method of disabling the user is non-reversable and not the desired behaviour for this scenario in particular.

]]> By: Damjan http://www.splee.co.uk/2006/09/07/disabling-users-instead-of-deleting/#comment-6831 Damjan Fri, 08 Sep 2006 20:00:46 +0000 http://www.splee.co.uk/2006/09/07/disabling-users-instead-of-deleting/#comment-6831 How about just changing the users password with adding a illegal character to it. The if you need to enable the user remove the character. How about just changing the users password with adding a illegal character to it. The if you need to enable the user remove the character.

]]> By: Splee http://www.splee.co.uk/2006/09/07/disabling-users-instead-of-deleting/#comment-6763 Splee Thu, 07 Sep 2006 15:04:18 +0000 http://www.splee.co.uk/2006/09/07/disabling-users-instead-of-deleting/#comment-6763 Because I want to be certain that the exception bubbles up to the SOProvider if the `self.by_email_address()` call raises an `SQLObjectNotFound`. It may still work your way but I\'m not certain of it. I will test it out later today. I can axe one line already by removing the `else:` clause but the readability increase is negligible. Because I want to be certain that the exception bubbles up to the SOProvider if the self.by_email_address() call raises an SQLObjectNotFound.

It may still work your way but I\’m not certain of it. I will test it out later today.

I can axe one line already by removing the else: clause but the readability increase is negligible.

]]> By: Matthias Urlichs http://www.splee.co.uk/2006/09/07/disabling-users-instead-of-deleting/#comment-6762 Matthias Urlichs Thu, 07 Sep 2006 14:32:29 +0000 http://www.splee.co.uk/2006/09/07/disabling-users-instead-of-deleting/#comment-6762 Why write eight lines, when four do the same thing and are (IMHO) much more readable? u = self.by_email_address(text) if u.disabled: raise SQLObjectNotFound return u Why write eight lines, when four do the same thing and are (IMHO) much more readable?

u = self.by_email_address(text)
if u.disabled:
    raise SQLObjectNotFound
return u
]]>