[Tickets #9548] Re: migration script db user rights

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/9548
------------------------------------------------------------------------------
  Ticket             | 9548
  Updated By         | rsalmon at mbpgroup.com
  Résumé             | migration script db user rights
  Queue              | Horde Base
  Version            | Git master
  Type               | Enhancement
  État               | Rejected
  Priorité           | 1. Low
  Milestone          |
  Patch              |
  Propriétaire       |
------------------------------------------------------------------------------


rsalmon at mbpgroup.com (2011-01-28 06:03) wrote:

> If this is not a problem, I can close this request? We might  
> consider adding user/password parameters to the migration script at  
> a later point.
I meant that it wasn't an issue to me the fact that the migration  
script uses the sql user configured in horde.

> But actually the Horde SQL user *always* needed at least CREATE  
> permissions to create sequence tables. I don't see a good reason to  
> grant CREATE and DELETE permissions but not ALTER permissions.

I Agree, and if horde sql user should have all the privileges needed  
to run the migration script, then the migration script doesn't need a  
user/password parameters.

So, since lots of admin/user are going to update to the new version of  
Horde, and the fact that up to now, horde sql user never had the ALTER  
privilege, can the migration script check for all needed sql privilege  
before running ?

This should prevent users from asking on the horde lists (or file a  
bug) because the migration script doesn't run correctly. Right now the  
migration script assume that sql user has all required privileges.