-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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-2081: Fix incorrect usage of appuser_id instead of created_by for m_savings_account_transaction table #4102
base: develop
Are you sure you want to change the base?
Conversation
@Jaswanth-Sriram-Veturi Would you mind to change the PR title and the commit message to the below? |
Also would you mind to create an integration test that covers the |
4bd3785
to
c527241
Compare
Done |
c527241
to
3740b6a
Compare
@Jaswanth-Sriram-Veturi Seems the query is not correct for postgres:
Would you mind to take a look at this? |
…y for m_savings_account_transaction table
3740b6a
to
b19dad8
Compare
Done |
This pull request seems to be stale. Are you still planning to work on it? We will automatically close it in 30 days. |
Description
Cashier transactions GET APIs
/v1/tellers/{tellerId}/cashiers/{cashierId}/transactions
and/v1/tellers/{tellerId}/cashiers/{cashierId}/summaryandtransactions
are throwing internal server error because old column name(appuser_id) is being used instead of new column name(created_by). The name of the column is changed hereSample requests
/v1/tellers/1/cashiers/1/summaryandtransactions?currencyCode=USD
/v1/tellers/1/cashiers/1/transactions?currencyCode=USD
Exception:
Ignore if these details are present on the associated Apache Fineract JIRA ticket.
Checklist
Please make sure these boxes are checked before submitting your pull request - thanks!
Write the commit message as per https://github.com/apache/fineract/#pull-requests
Acknowledge that we will not review PRs that are not passing the build ("green") - it is your responsibility to get a proposed PR to pass the build, not primarily the project's maintainers.
Create/update unit or integration tests for verifying the changes made.
Follow coding conventions at https://cwiki.apache.org/confluence/display/FINERACT/Coding+Conventions.
Add required Swagger annotation and update API documentation at fineract-provider/src/main/resources/static/legacy-docs/apiLive.htm with details of any API changes
Submission is not a "code dump". (Large changes can be made "in repository" via a branch. Ask on the developer mailing list for guidance, if required.)
FYI our guidelines for code reviews are at https://cwiki.apache.org/confluence/display/FINERACT/Code+Review+Guide.