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

* Your Email Address
* Spam protection	Enter the letters below: . .. ..__ .___. __ \| \|\|__\|[__) _/ / ` \|__\|\| \|\| \./__.\__.
Comment	>> >>> 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)
Attachment
Watch this ticket