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

noreply at bugs.horde.org noreply at bugs.horde.org
Wed Jul 9 23:29:31 UTC 2014


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

Ticket URL: http://bugs.horde.org/ticket/13331
------------------------------------------------------------------------------
  Ticket             | 13331
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  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             |
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2014-07-09 23:29) wrote:


> On the one hand, I understand your position. It's never been  
> removed, so you keep the schema updated.

Yes, since some installations may have explicitly kept using the  
"legacy" share driver.

> but if data is lost when switching between NG and non-NG (no data is  
> migrated between tables),

If you run NG for some period of time and then switch back to non-NG,  
yes, then any new shares or perms that were changed since the switch  
to NG would be lost.  The idea of having both drivers isn't to allow  
admins to switch back and forth at will, but rather to give a choice  
in drivers. Originally, IIRC, some fringe cases were showing better  
performance with the original driver (though this has probably changed  
since then), so we continued to provide, and maintain both drivers.

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.






More information about the bugs mailing list