Hi all -

I wanted to revisit this conversation.I have been working on this
migration, and there are 2 possible approaches that we can take.

1) Require the user to turn off ONLY_FULL_GROUP_BY in sql_mode for the
MySQL instance (in /etc/mysql/my.cnf for most users). As of MySQL 5.7.5
this is turned on by default. The advantage of this approach is that it
requires only 1 change to migration files, and reduces the risks (as
pointed out by Nikhil and others) of breaking Read Platform services,
Pentaho reports, and any other externally configured queries.

2) Use the default settings where ONLY_FULL_GROUP_BY is on. This requires
more changes to the migration scripts and would require more testing of
external services and reports.

The following link gives some good background on ONLY_FULL_GROUP_BY -
http://rpbouman.blogspot.nl/2014/09/mysql-575-group-by-respects-functional.html

My recommendation would be to leave ONLY_FULL_GROUP_BY on and do the
thorough testing that is required. However, I welcome your input and
thoughts.
Thanks,
Steve


On Wed, Jan 17, 2018 at 8:00 PM, Nikhil Pawar <nickr...@gmail.com> wrote:

> Hi Steve,
>
> +1 from my side as well.
> I think the areas where the application directly interacts with database (
> w/o any intermediate layer like OpenJPA) would be more vulnerable.
> The places to look out according to me would be:
>  1) Migration scripts (which you are already aware of)
>  2) Various ReadPlatform services wherein we have written SQLs to fetch
> data from database.
> 3) Pentaho Reports (not quite sure about it but this module needs to be
> thoroughly tested after migration).
>
> Regards,
> Nikhil
>
>
>
> On Wed, Jan 17, 2018 at 8:48 AM, Steve Conrad <sconr...@gmail.com> wrote:
>
> > To the Mifos and Fineract dev communities -
> >
> > My name is Steve Conrad, and I have recently begun volunteering with the
> > Mifos/Fineract community and really appreciate the great work that you
> all
> > are doing.
> >
> > I wanted to propose a new project to migrate the Fineract platform to
> MySQL
> > 5.7. There are several features in MySQL 5.7 that would benefit the
> project
> > - performance, embedded JSON objects in the schema, multithreaded
> > replication, among others.
> >
> > When I installed Fineract locally, I used MySQL 5.7. I had to change a
> few
> > of the database migration scripts. I have obviously not gone through all
> of
> > the use cases, but so far am running with no issues.
> >
> > Does anyone know of any reasons why we could not move to MySQL 5.7?
> > Obviously there would be a large testing task, but it may be a worthwhile
> > investment to keep the Fineract platform current.
> >
> > Thanks,
> > Steve
> >
>

Reply via email to