# Seeking suggestions on alternative for my parent-child model situation **URL:** \ **Category:** Elasticsearch\ **Created:** [December 12, 2018, 2:27pm UTC](https://discuss.elastic.co/t/seeking-suggestions-on-alternative-for-my-parent-child-model-situation/160558 "2018-12-12T14:27:58Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![avenky](https://avatars.discourse-cdn.com/v4/letter/a/d6d6ee/32.png) [@avenky](https://discuss.elastic.co/u/avenky)\ **Post date:** [December 12, 2018, 2:27pm UTC](https://discuss.elastic.co/t/seeking-suggestions-on-alternative-for-my-parent-child-model-situation/160558/1 "2018-12-12T14:27:58Z")
Hi All, #0. Accounts Details (slowly changing dimension) | | | | ---\> #1. Balances (daily snapshot - truncated and loaded daily) | | ---\> #2. Transactions (history data - appended daily) | | ---\> #3. Access Control List (list of users who can view any given account - changes frequently) Only the users who have access to an account as per #3 should be able to see #0,#1 and #2 of any given account. I was originally thinking about implementing parent-child for this (#0 being parent and 1,2,3 being children). But I read in forums that it is not one of encouraged practice. So, I am looking for alternate suggestions. If I have to think of separate indexes for each of them, I can nest in #3 into #0 and #1. But cant do the same for #2, as it is historically built data. Seeking expert opinions and suggestions. thanks in advance. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [January 9, 2019, 2:28pm UTC](https://discuss.elastic.co/t/seeking-suggestions-on-alternative-for-my-parent-child-model-situation/160558/2 "2019-01-09T14:28:04Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.