|
||||||||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||||||||
------------------------------------------------------------------------------ Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter
_______________________________________________ Mifos-issues mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mifos-issues
vishwas picked up on the following things:
1. The idea was to create a one-to-one table to add additional fields to the m_loan_transaction table in order to capture extra transaction details based on the type of transaction that happened (cash, cheque, receipt, ELECTRONIC_FUND_TRANSFER) but you have used a many to one relationship
2. The table to capture additional details was called m_payment_detail? shouldnt it be m_loan_transaction_detail?
3. Some fields on the additional table you expect naturally to be unique such as receipt_number, cheque_number, routing_code but have no constraints on them