| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Ibrahim Shaame <ishaame(at)gmail(dot)com> |
| Cc: | swastik Gurung <gurung_swastik(at)yahoo(dot)com>, "pgsql-novice(at)lists(dot)postgresql(dot)org" <pgsql-novice(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Reporting by family tree |
| Date: | 2023-10-25 14:54:42 |
| Message-ID: | CAKFQuwamjM=d9RHDc+OHEkeWiCGpQJL=sMSxJ_tzwETrx=75Ww@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
On Wed, Oct 25, 2023 at 5:21 AM Ibrahim Shaame <ishaame(at)gmail(dot)com> wrote:
> But what I want to get is grandfather - father - children:
>
> 1 - Grandfather1
>
> 3 - father1-1
>
> 6 - son1-1
>
> 7 – son1-2
>
> 4 - Father1-2
>
> 8 - son2-1
>
> 2 – Grandfather2
>
> 5 - Father2-1
>
> etc
>
>
> Any suggestion
>
>
If you want a different ordering of the output change the ORDER BY
specification.
Specifically, you want to order by the path of each person. Since that can
only be determined during the traversal you need to create the path data
yourself. I suggest using an integer[] (integer array) to store the path
using ID values as breadcrumbs.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | o1bigtenor | 2023-10-25 16:13:08 | Re: Reporting by family tree |
| Previous Message | Ibrahim Shaame | 2023-10-25 12:20:30 | Re: Reporting by family tree |