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	> >> 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. >
Attachment
Watch this ticket