ok, so we will have to add an upgrade 431to440 which is identical to
430to440. This would be only an entry in the map, no extra classes
needed, i would imagine.
On Mon, Jun 30, 2014 at 6:02 PM, David Nalley wrote:
> Well, if the DB reports it's version 4.3.1, it will have no upgrade
> path to 4.4
Well, if the DB reports it's version 4.3.1, it will have no upgrade
path to 4.4.0 and will fail. Unless something has changed very
recently.
--David
On Mon, Jun 30, 2014 at 10:49 AM, Daan Hoogland wrote:
> at the moment there is no special case for 4.3.1 to 4.4 (.0 or .1)
>
> On Mon, Jun 30, 201
at the moment there is no special case for 4.3.1 to 4.4 (.0 or .1)
On Mon, Jun 30, 2014 at 3:22 PM, sebgoa wrote:
>
> On Jun 18, 2014, at 6:19 AM, Koushik Das wrote:
>
>> 4.3.1 -> 4.4.0 upgrade also needs to be handled.
>>
>
> Daan pushed a 4.3.0 to 4.3.1 in the 4.3 branch just now.
>
> the 4.3.
On Jun 18, 2014, at 6:19 AM, Koushik Das wrote:
> 4.3.1 -> 4.4.0 upgrade also needs to be handled.
>
Daan pushed a 4.3.0 to 4.3.1 in the 4.3 branch just now.
the 4.3.1 to 4.4.0 needs to be in the 4.4 branch (maybe even the RC of 4.4.0)
or it will go in 4.4.1
yes ?
> -Original Message-
So far it is the same as 4.3.0 -> 4.4.0
On Wed, Jun 18, 2014 at 6:19 AM, Koushik Das wrote:
> 4.3.1 -> 4.4.0 upgrade also needs to be handled.
>
> -Original Message-
> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> Sent: Tuesday, 17 June 2014 9:16 PM
> To: dev
> Subject: [ACS431][
4.3.1 -> 4.4.0 upgrade also needs to be handled.
-Original Message-
From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
Sent: Tuesday, 17 June 2014 9:16 PM
To: dev
Subject: [ACS431][QUESTION] db upgrace
In my simple mind it seems we only need to create a Upgrade430to431.java file
and d
