I've updated the wiki page to reflect this. Sorry for not including this in Breaking Changes at release time.
B. On 9 April 2012 09:41, Benoit Chesneau <[email protected]> wrote: > On Mon, Apr 9, 2012 at 9:16 AM, Dirkjan Ochtman <[email protected]> wrote: >> On Mon, Apr 9, 2012 at 15:12, Dirkjan Ochtman <[email protected]> wrote: >>> I was just trying to upgrade the first of my servers to 1.2, and it >>> wasn't that pretty. As I understand it, compatibility with pre-0.10.0 >>> databases has been dropped. However, this isn't mentioned in the >>> release notes, nor in the Breaking changes. Thus, I had to downgrade >>> to 1.1.1, compact a database and install 1.2.0 again. This is just a >>> PITA, and it seems fairly trivial that something like this should be >>> in the release notes and in the breaking changes. >> >> Forgot to mention something I'm not sure is an issue, but should be >> checked: how resistant is CouchDB against inaccessible _users or >> _replicator? It seems like even _users might at some point be in an >> unsupported on-disk version. I run all of my couches in Admin Party >> mode so I never even look at the _users database, but it probably >> wouldn't work all that well. >> >> Cheers, >> >> Dirkjan > > Hi Dirkjan, > > Your probably right about the user migrations. Basically if your use > document doesn't have any owner doc a normal user won't be abble to > update it. On the other hand it should still be possible to > update/delete them with an admin. > > > Can ou create separate issues about this on jira ? (one for migration > , and the other for the users db migration) ? It will help to track > the problem. > > - benoît
