Mailing-List: contact issues-help@fineract.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@fineract.incubator.apache.org
From: terencemo <git@git.apache.org>
To: issues@fineract.incubator.apache.org
Reply-To: issues@fineract.incubator.apache.org
Message-ID: <git-pr-154-incubator-fineract@git.apache.org>
Subject: [GitHub] incubator-fineract pull request #154: Fixed client share activated user join
Content-Type: text/plain
Date: Wed, 22 Jun 2016 09:40:47 +0000 (UTC)
archived-at: Wed, 22 Jun 2016 09:40:52 -0000

GitHub user terencemo opened a pull request:

    https://github.com/apache/incubator-fineract/pull/154

    Fixed client share activated user join

    When getting share account list under a client, if ```rejected_userid``` is set for the share account, the join condition for ```activated_userid``` was using the rejected user table in the join condition resulting in multiple instances of share account records which have both these columns set. Also the activated user details are incorrectly returned in the resultset. The fix uses the correct table alias avbu in the join condition instead of rbu and so removes duplicate records and ensures correct activated user details are returned.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/terencemo/incubator-fineract i190-multi-shareac

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-fineract/pull/154.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #154
    
----
commit 34353938a7788520c53f07ff95fef9862d9cf539
Author: Terence Monteiro <terence@sanjosesolutions.in>
Date:   2016-06-22T08:32:22Z

    Fixed client share activated user join

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---