Thanks Arnold for driving these contributions and being so transparent and deliberate in keeping the community informed.
It's a great model and example for all of us in the community on contributing large changes upstream. Ed On Tue, Feb 22, 2022, 14:35 Petri Tuomola <petri.tuom...@gmail.com> wrote: > Great work! Very excited to see these changes - it will be an excellent > addition and should bring a lot of benefits wrt performance. > > Also with Postgres we do not need to worry about bundling the JDBC drivers > as they are all BSD licensed. > > Thanks again for your contributions! > > Regards > Petri > > On 21 Feb 2022, at 16:24, Aleksandar Vidakovic <chee...@monkeysintown.com> > wrote: > > ... looking forward to seeing these changes Arnold. Thanks again for all > the work! > > On Mon, Feb 21, 2022 at 8:59 AM Arnold Galovics <galovicsarn...@gmail.com> > wrote: > >> Dear Community, >> >> As I mentioned a couple of mails back, it would be awesome if Fineract >> could support PostgreSQL because of the performance gain it could bring. >> >> The first milestone in this process was to make the database migrations >> MySQL independent and switch from Flyway to Liquibase. That's done, thanks >> for reviewing and merging the changes. >> >> Now, I'm planning to continue on this path slowly but surely. In the >> upcoming days/weeks I'm going to be filing new PRs to make Fineract as >> independent as possible from MySQL and rely on standard SQL tools. Just as >> an example, MySQL supports the IFNULL function but PostgreSQL doesn't. >> However, IFNULL can be easily replaced by the ANSI SQL COALESCE function >> which is supported both by MySQL and PostgreSQL. >> >> The JIRA I'm using for creating the commits is FINERACT-984 >> <https://issues.apache.org/jira/browse/FINERACT-984>. >> Also, the first PR has landed already in develop: PR link >> <https://github.com/apache/fineract/pull/2039> >> >> Best, >> Arnold >> > >
