[
https://issues.apache.org/jira/browse/FINERACT-902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17092655#comment-17092655
]
Michael Vorburger commented on FINERACT-902:
--------------------------------------------
Nice, yeah the more fine grained fetch=FetchType.LAZY annotation is definitely
a better solution than the original global persistence.xml change. Of course,
this still changes other existing queries on the m_savings_account table
(SavingsAccount). So in theory, it would have been even nicer to use a "Fetch
Plan" to only affect the query from your new code. In practice however, without
being able to (easily) measure the impact, I'm fine with that solution.
Specifically because I guess it's theoretically possible that it actually even
improves instead of worsens performance. It all depends on how often that JOIN
is really required, and when it's superflous (which you could control much more
fine grained with a Fetch Plan, for each time the domain object is queried).
But let's leave that for a later enhancement, I've opened new FINERACT-912
about it, so that we can close this issue.
> Fix error "MySQL can only use 61 tables in a join hibernate"
> ------------------------------------------------------------
>
> Key: FINERACT-902
> URL: https://issues.apache.org/jira/browse/FINERACT-902
> Project: Apache Fineract
> Issue Type: Bug
> Reporter: Rahul Pawar
> Priority: Major
>
> Error: "MySQL can only use 61 tables in a join hibernate" in PR
> [https://github.com/apache/fineract/pull/738].
> This error occurred due to two new tables - glim_accounts and gsim_accounts
> and they had Foreign Key with Gigantic tables Loan and Savings account which
> caused this exception.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
