[
https://issues.apache.org/jira/browse/FINCN-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16951924#comment-16951924
]
Michael Vorburger edited comment on FINCN-26 at 10/15/19 1:35 PM:
------------------------------------------------------------------
[~ikamga] I haven't followed the transition from MariaDB to PostgreSQL in
Fineract CN in full details, but seeing PRs such as e.g.
[https://github.com/apache/fineract-cn-payroll/pull/9] or
[https://github.com/apache/fineract-cn-portfolio/pull/15] indeed make it look
like this happened...
However I'm still seeing [https://github.com/apache/fineract-cn-mariadb,]
what's the role of that repo, should it be removed/archived? Also in
[https://github.com/apache/fineract-cn-demo-server/search?utf8=%E2%9C%93&q=mariadb&type=]
there are still a lot of references to mariadb - perhaps you'd like to clean
those up?
Other than that, I have no objection if you then close this issue.
was (Author: vorburger):
[~ikamga] I haven't followed the transition from MariaDB to PostgreSQL in
Fineract CN in full details, but seeing PRs such as e.g.
[https://github.com/apache/fineract-cn-payroll/pull/9] or
[https://github.com/apache/fineract-cn-portfolio/pull/15] indeed make it look
like this happened... however I'm still seeing
[https://github.com/apache/fineract-cn-mariadb,] what's the role of that repo,
should it be removed/archived? Also in
[https://github.com/apache/fineract-cn-demo-server/search?utf8=%E2%9C%93&q=mariadb&type=]
there are still a lot of references to mariadb - perhaps you'd like to clean
those up?
Other than that, I have no objection if you then close this issue.
> Replace MariaDB driver with drizzle as JDBC driver
> --------------------------------------------------
>
> Key: FINCN-26
> URL: https://issues.apache.org/jira/browse/FINCN-26
> Project: Fineract Cloud Native
> Issue Type: Task
> Components: fineract-cn-mariadb
> Reporter: Myrle Krantz
> Assignee: Isaac Kamga
> Priority: Blocker
>
> Fineract CN currently depends on 'org.mariadb.jdbc:mariadb-java-client:1.4.3'
> as our JDBC driver. It's for our connection to an SQL database, and can be
> used for MySQL as well as MariaDB. This component is licensed as LGPL, and
> therefore, needs to be replaced before we release. The current suggestion is
> to replace it with drizzle. Other suggestions are also welcome.
> Why can't we have dependencies to LGPL software? This sequence of events
> would be bad:
> 1.) We include LGPL software in our release.
> 2.) Our code, including the LGPL dependency is included in proprietary code
> of CompanyOmega
> 3.) Some judge somewhere decides that the "firewall" separating our code from
> the LGPL isn't strong enough to call prevent the viral aspects of LGPL from
> taking effect.
> 4.) CompanyOmega's proprietary code is now all open source and they go out of
> business.
> It's not a likely sequence, but because of the size of the negative outcome,
> we avoid it by not including LGPL (or any other Category X software) in our
> releases.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
