OK thanks.
On Tue, Mar 28, 2017 at 9:30 AM, Martin Van Aken
wrote:
> That was from memory, hence the lack of details, sorry for that. I'll get
> my 2.24 instance back and send you the exact messages.
>
> Regards,
>
> Martin
>
> On Tue, Mar 28, 2017 at 3:12 PM, Lars Helge Øverland
> wrote:
>
>>
Hi Martin,
going directly from 2.22 -> 2.24 should in theory be fine, as we retain all
the update statements in the source code. Look for TableAlteror.java.
Could you paste the actual SQL errors you get during update? I am sure we
can work around this without upgrading to each instance.
regards,
That was from memory, hence the lack of details, sorry for that. I'll get
my 2.24 instance back and send you the exact messages.
Regards,
Martin
On Tue, Mar 28, 2017 at 3:12 PM, Lars Helge Øverland wrote:
> Okay. Which ones - could you paste the exact errors?
>
> On Tue, Mar 28, 2017 at 9:12 A
Okay. Which ones - could you paste the exact errors?
On Tue, Mar 28, 2017 at 9:12 AM, Martin Van Aken
wrote:
> Hi,
> Thanks a lot for the quick answer. On server start (2.24 server on a 2.22
> DB) I get errors such as: "cannot run ALTER TABLE table XXX contains null
> values".
>
> From my unders
Hi,
Thanks a lot for the quick answer. On server start (2.24 server on a 2.22
DB) I get errors such as: "cannot run ALTER TABLE table XXX contains null
values".
>From my understanding of the release notes, looks like 2.23 was
creating/populating some columns and 2.24 putting them as not null, corr
Hello,
We're upgrading a 2.22 instance to 2.24.
Looking at the release notes, 2.23 has a SQL to run for ProgramIndicators
(which we don't have) but 2.24 warns about setting some columns as "not
null" and that those should be filled by the 2.23. To avoid installing each
version in turn, is there any
6 matches
Mail list logo
