Sat, 04 Apr 2026 11:52:06 +0000 https://bugs.horde.org/ticket/13331 Upgrade fails because script doesn't recognise name of shares tables Here is the message I get when trying to update the database schemas SQLSTATE[42S02]: Base table or view not found: 1146 Table 'webmail.turba_shares' doesn't exist In our database, all the "shares" tables are named sharesng. It probably happened when converting the backend from datatree to SQL. Tue, 08 Jul 2014 20:17:11 +0000 https://bugs.horde.org/ticket/13331#t84533 If you don't have that table, you didn't migrate properly in the past. You must migrate from an up-to-date Horde 3 version, as clearly documented in the upgrade instructions. Wed, 09 Jul 2014 09:17:07 +0000 https://bugs.horde.org/ticket/13331#t84551 > If you don't have that table, you didn't migrate properly in the > past. You must migrate from an up-to-date Horde 3 version, as clearly > documented in the upgrade instructions. We've migrated properly in the past, but then switched to using sharesng and removed the old shares tables which only contained duplicated data. Where are the old tables used? They were never kept in sync with the new ones Wed, 09 Jul 2014 22:53:25 +0000 https://bugs.horde.org/ticket/13331#t84590 > 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. Wed, 09 Jul 2014 23:00:02 +0000 https://bugs.horde.org/ticket/13331#t84591 > >> 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) Wed, 09 Jul 2014 23:16:05 +0000 https://bugs.horde.org/ticket/13331#t84592 > 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. Wed, 09 Jul 2014 23:29:31 +0000 https://bugs.horde.org/ticket/13331#t84593 > 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. Wed, 09 Jul 2014 23:43:49 +0000 https://bugs.horde.org/ticket/13331#t84595