[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:16) wrote:

>
>> We've migrated properly in the past, but then switched to using
>> sharesng and removed the old shares tables which only contained
>> duplicated data.
>
> You shouldn't perform operations like this outside of migrations.
>
>> Where are the old tables used? They were never kept in sync with  
>> the new ones
>
> They are used if the installation is not using the "next generation"  
> share driver. Both are still maintained.

On the one hand, I understand your position. It's never been removed,  
so you keep the schema updated, but if data is lost when switching  
between NG and non-NG (no data is migrated between tables), then maybe  
it would be best to update the schemas of what the installation is  
using and to use scripts to migrate from one backend to another?

(I haven't checked if data is copied over when switching backend)