[Tickets #13331] Re: Upgrade fails because script doesn't recognise name of shares tables

[noreply at bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/13331
------------------------------------------------------------------------------
  Ticket             | 13331
  Updated By         | software-horde at interfasys.ch
  Summary            | Upgrade fails because script doesn't recognise name of
                     | shares tables
  Queue              | Horde Groupware Webmail Edition
  Version            | 5.2.0
  Type               | Bug
  State              | Not A Bug
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


software-horde at interfasys.ch (2014-07-09 23:43) wrote:

> This is no different than supporting different database backends, or  
> address book backends, or authentication backends etc... Just  
> because we provide different drivers to switch between doesn't mean  
> that data should be somehow automagically preserved when switching.
>
> That being said, we DO offer a script that can convert between  
> non-ng and ng shares at will. We just don't offer the backwards  
> conversion at will since the idea is to move everyone towards the  
> new driver anyway.
>
I think I see what you mean. You want to keep the structure of as many  
backends as possible updated, to make it easy to switch from one to  
another.
 From my point of view, any structure check/migration could be  
performed when the driver is changed or the data migrated via the  
scripts you provide, but in this case, since the tables are so  
similar, I can understand how it's easier to maintain that way,  
instead of modifying the configuration scripts.