[
https://issues.apache.org/jira/browse/FINERACT-604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16817043#comment-16817043
]
Bharath Kumar commented on FINERACT-604:
----------------------------------------
Dear Team,
I have tried migrating this code into mifos x version 17 but still i get the
issue in the pentaho reports. It would be a really great help if i get any help
from the mifos community to resolve the issue
I getting this error message when i try to open a particular report
{
"timestamp": 1555181938122,
"status": 500,
"error": "Internal Server Error",
"exception": "org.springframework.jdbc.BadSqlGrammarException",
"message": "StatementCallback; bad SQL grammar [select x.* from (select
sp.parameter_name, sp.parameter_variable, sp.parameter_label,
sp.parameter_displayType, \r sp.parameter_FormatType, sp.parameter_default,
sp.selectOne, sp.selectAll, spp.parameter_name as parentParameterName\r from
stretchy_parameter sp\r left join stretchy_parameter spp on spp.id =
sp.parent_id\r where sp.special is null\r and exists \r \t(select 'f' \r \tfrom
stretchy_report sr\r \tjoin stretchy_report_parameter srp on srp.report_id =
sr.id\r \twhere sr.report_name in('Client Listing(Pentaho)')\r \tand
srp.parameter_id = sp.id\r \t)\r order by sp.id) x]; nested exception is
com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table
'mifostenant-default.sp' doesn't exist"
}
But the same query works fine for the mysql version 5.6. I am really confused
can any one assists with this issue. Waiting for a response from the community.
Thanks in advance
Thanks and Regards,
V Bharath Kumar
> Support for MySQL 5.7
> ---------------------
>
> Key: FINERACT-604
> URL: https://issues.apache.org/jira/browse/FINERACT-604
> Project: Apache Fineract
> Issue Type: Improvement
> Affects Versions: 1.0.0
> Environment: MySQL version 5.7.5 or higher
> Reporter: Steve Conrad
> Assignee: Santosh Math
> Priority: Major
> Labels: gsoc, p1
> Fix For: 1.2.0
>
>
> Provide support for MySQL 5.7. This includes all migrations scripts, services
> code, and reports. The core issue is support for strict mode in MySQL
> (ONLY_FULL_GROUP_BY enabled).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
