Hi Ippez,

I would like to add more information about the issue that you faced and someone 
can save some time in the future .

Mifos X has been running and tested to run "as is" using MySQL (version 5.5 or 
5.6) Check this link 
https://mifosforge.jira.com/wiki/spaces/MDZ/pages/92504091/Prerequisite

MariaDB which is a fork of MySQL over the time have diverged and the JDBC 
drivers and Hibernate dialects are different check this other link 
http://in.relation.to/2017/02/16/mariadb-dialects/

In the code of Mifos X (fineract-provider) you can find 
org.hibernate.dialect.MySQLDialect which now could lead to non expected results 
while using MariaDB (just like in the Reports)

If you want to run Mifos X without any DB issue, you have to use MySQL 5.5 or 
5.6 but if you want to use MariaDB some fixes must be applied in the Mifos 
source code, drivers and dependencies.

For now, use the recommended MySQL version 5.5 or 5.6 for running Mifos X 
18.03.01

Victor Romero

El 30/04/18 a las 00:58, Victor Manuel Romero Rodriguez escribió:

Hi Ippez,


Could you please confirm which is the version of MariaDB? MySQL ? that
you are running? Also the JDBC driver version please.

Victor


El 28/04/18 a las 04:34, Ippez Robert escribió:


I found out a solution and i thought this may be helpful to other community
members. It has been been caused As of XAMPP 5.5.30 and 5.6.14, XAMPP ships
MariaDB instead of MySQL.

Solution can be found here
<https://gist.github.com/odan/c799417460470c3776ffa8adce57eece><https://gist.github.com/odan/c799417460470c3776ffa8adce57eece>

On Sat, Apr 28, 2018 at 9:18 AM, Ippez Robert 
<[email protected]><mailto:[email protected]> wrote:



I found out a similar issue raised here http://mail-archives.
apache.org/mod_mbox/fineract-dev/201609.mbox/%3CCALjGkK2oxy-Lxg_=vui6UD+
[email protected]%3E<mailto:[email protected]%3E>
but there seems no solution given.

On Sat, Apr 28, 2018 at 5:53 AM, Ippez Robert 
<[email protected]><mailto:[email protected]>
wrote:



Sure. it's the latest branch that i built. Can any please have a look at
this. I remember sometime back people experienced the same and from the
discussion threads I followed, it's caused as a result of either database
driver mariaDB or mysql. Not sure how this was fixed, where can i find the
PR for this fix?

Thanks
Regards
Ippez Robert

On 28 Apr 2018 01:33, "Victor Romero" 
<[email protected]><mailto:[email protected]>
wrote:



Hi Ippez,

This is happening in Mifos X 18.03.01?

Could you confirm the version?

Regards

Victor

⁣Enviado desde TypeApp ​

En abr. 27, 2018 2:27 PM, en 2:27 PM, Ippez Robert <
[email protected]<mailto:[email protected]>> escribió:


Hi All,
All our reports don't work. We are not sure why this is happening. They
don't display even if you click on *Reports>>Al*l menu. The error we
get is
org.springframework.jdbc.BadSqlGrammarException: StatementCallback; bad
SQL grammar [select x.* from (select parameter_sql as the_sql from
stretchy_parameter where parameter_name = 'FullReportList') x]; nested
exception is com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException:
Table 'mifostenant-default.x' doesn't exist

I have pasted complete error log here 
<https://pastebin.com/Xez76bDj><https://pastebin.com/Xez76bDj>.
Any
assistance will be highly appreciated

Regards
Ippez Roberts


-----------------------------------------------------------


-------------


-----------------------------------------------------------


-------------------


Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

-----------------------------------------------------------


-------------


Mifos-developer mailing list
[email protected]<mailto:[email protected]>
Unsubscribe or change settings at:
https://lists.sourceforge.net/lists/listinfo/mifos-developer



--
Ippez Roberts
Founder/C.E.O - Swift3 Technologies (U) Ltd
"Redefining Next Generation I/O Systems"
P.O.Box 155, Moyo
UGANDA.
Tel: +256788725408/770602630
Skype ID: ippez.robert1
Email: [email protected]<mailto:[email protected]>










Reply via email to