Re: [4.6.1/4.7.0] Database upgrade path issues/forks between 4.6.0/4.6.1 and 4.7.0/master

2015-12-04 Thread Daan Hoogland
I gave it a quick shot. A test build is running and I'll create the pr in a minute. On Fri, Dec 4, 2015 at 9:51 AM, Rohit Yadav wrote: > Hi Daan, I’m testing quota but can work on it in 1-2 hours. So, not > started yet but if you got time go ahead, and later I can help review/merge > your PR. >

Re: [4.6.1/4.7.0] Database upgrade path issues/forks between 4.6.0/4.6.1 and 4.7.0/master

2015-12-04 Thread Rohit Yadav
Hi Daan, I’m testing quota but can work on it in 1-2 hours. So, not started yet but if you got time go ahead, and later I can help review/merge your PR. Regards. On 04-Dec-2015, at 2:15 PM, Daan Hoogland mailto:daan.hoogl...@gmail.com>> wrote: Rohit, First of all good catch. I think we need to

Re: [4.6.1/4.7.0] Database upgrade path issues/forks between 4.6.0/4.6.1 and 4.7.0/master

2015-12-04 Thread Daan Hoogland
Rohit, First of all good catch. I think we need to remove the 460to470 step and have the path always pass by 4.6.1. Are you busy with this change already? On Fri, Dec 4, 2015 at 6:03 AM, Rohit Yadav wrote: > There seems to be a db view related change between 4.6.0 and 4.6.1 (DB) > versions; and

[4.6.1/4.7.0] Database upgrade path issues/forks between 4.6.0/4.6.1 and 4.7.0/master

2015-12-03 Thread Rohit Yadav
There seems to be a db view related change between 4.6.0 and 4.6.1 (DB) versions; and there exists separate DB upgrade paths from 4.6.0 to 4.7.0 and 4.6.1 to 4.7.0 on master branch which shares the same changes. The issue is that the upgrade path from 4.6.0 to 4.7.0 does not include the db view