[Tickets #6967] Re: user data removal patch

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/6967
------------------------------------------------------------------------------
  Ticket             | 6967
  Updated By         | vilius at lnk.lt
  Summary            | user data removal patch
  Queue              | Horde Framework Packages
  Version            | HEAD
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


vilius at lnk.lt (2008-06-26 06:53) wrote:

> As far as I understand from Chuck's comment, you only need this
> because you are using the cyrsql driver and don't want to stop
> removing the user if parent::removeUser() is returning an error due
> to the removeUserData() call in the sql driver. Is this correct?

Yes.

> But you patch unconditionally removes returning errors from
> Auth_sql::removeUser() so this won't report any errors for people
> using the sql driver directly. This is of course not acceptable.

Ghm, correct me if I'm wrong but isn't application's removeUserData()  
call reports these errors anyway? With my patch and *without*  
http://bugs.horde.org/ticket/6968 patches I'm still getting errors  
from nag, mnemo etc. BUT the user is removed succefully from the  
backend. What is the difference between calling removeUser() from  
Auth_cyrsql and Auth_sql? As I see in the source it executes exactly  
the same API call in the needed applications.