Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FINERACT-1135: Fix SQL error at loan repayment template #1296

Merged

Conversation

francisguchie
Copy link
Contributor

Description

https://issues.apache.org/jira/browse/FINERACT-1135

Checklist

Please make sure these boxes are checked before submitting your pull request - thanks!

Our guidelines for code reviews is at https://cwiki.apache.org/confluence/display/FINERACT/Code+Review+Guide

@awasum awasum requested review from ptuomola and xurror August 27, 2020 20:12
Copy link
Contributor

@xurror xurror left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks OK to me.

@awasum
Copy link
Contributor

awasum commented Aug 27, 2020

Minor feedback for now and the future, Always use the issue number in all caps when using it in a commit message: FINERACT-1135: Fix Error at Loan Repayment will be commit message or Fix Error at Loan Repayment (FINERACT-1135) as in upcoming: #1284

sqlBuilder.append(
" l.currency_code as currencyCode, l.currency_digits as currencyDigits, l.currency_multiplesof as inMultiplesOf, rc.`name` as currencyName, ");
sqlBuilder.append(" rc.display_symbol as currencyDisplaySymbol, rc.internationalized_name_code as currencyNameCode ");
sqlBuilder.append(" FROM m_loan l");
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a reason for removing all these spaces from beginning of the strings? The reason for them, as far as I can see, is avoiding a situation where someone adds before a string that doesn't have a space at the end, and causes the next string to therefore generate broken SQL. I don't think they are harmful and can save us from some accidental illegal SQL...

@francisguchie
Copy link
Contributor Author

Minor feedback for now and the future, Always use the issue number in all caps when using it in a commit message: [FINERACT-1135](https://issues.apache.org/jira/browse/FINERACT-1135): Fix Error at Loan Repayment will be commit message or Fix Error at Loan Repayment ([FINERACT-1135](https://issues.apache.org/jira/browse/FINERACT-1135)) as in upcoming: #1284

thanks @awasum

Copy link
Contributor

@ptuomola ptuomola left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ptuomola ptuomola changed the title Fineract-1135 error at loan repayment FINERACT-1135: Fix SQL error at loan repayment template Sep 1, 2020
@ptuomola ptuomola merged commit 2e720e3 into apache:develop Sep 1, 2020
@vidakovic
Copy link
Contributor

@francisguchie any chance to get this backported to the release branch 1.4.0? The Jira ticket for that is still open... would appreciate if we could do this soon to push the release over the finish line. Thanks.

@godiraonedipuo
Copy link

Good day, am failing to import LoanRepayment on fineract using template. This is the screenshot of my template download after it fails to upload the records.

Monosnap 7d0ab762-b2e1-42f7-86d4-974a626f23f6 xls

Thank you, your support is highly appreciated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants