Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1r6tFF-0032WJ-G4 for pgsql-novice@arkaria.postgresql.org; Sat, 25 Nov 2023 14:02:53 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1r6tFC-002eJP-NB for pgsql-novice@arkaria.postgresql.org; Sat, 25 Nov 2023 14:02:50 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1r6tFC-002eJH-Cx for pgsql-novice@lists.postgresql.org; Sat, 25 Nov 2023 14:02:50 +0000 Received: from mail-oo1-xc33.google.com ([2607:f8b0:4864:20::c33]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1r6tF9-008Sxt-Lj for pgsql-novice@lists.postgresql.org; Sat, 25 Nov 2023 14:02:49 +0000 Received: by mail-oo1-xc33.google.com with SMTP id 006d021491bc7-58d6b0df182so5883eaf.0 for ; Sat, 25 Nov 2023 06:02:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1700920965; x=1701525765; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=tdL0iK0q14ddG2Ui0MTDr7GpKCTdXWC6znuLeEOQnG0=; b=etmymUa9gDqA/9KpDfep/buxzBJxzBK8TP430vJ/9kUcQjyt/AsvkFX0KgrImf2Ycj hs2WmjOBENA4/RTDgzpbFNyEKrW265G1bUOnrikJV0cJHim1CnIDezhV7dFi/l2fpZF1 2zX+CcPHoliv+pNf1ABMLQTu92Pgk+Yh/unGtc7qT4PLxerUwpWJH+yg28TX8HTYrj0V xepKsXleKurY/kVkr4wColnqpWWCJl2N++hbNwH0J3rTooz3T3UKdY/zPoNPEl6fmuAg FMLb2CS2AkjRAOc/xR3N+huMxWaW6J5B8CU0ujRzabM/tSiZG+sw+9Q0lLLEzAFVWH9r wxjw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700920965; x=1701525765; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=tdL0iK0q14ddG2Ui0MTDr7GpKCTdXWC6znuLeEOQnG0=; b=XkTDoZWyhTK1JxQsPcOD6Eyq2+qW103Pe4uix9TYoHb3wf1+Cigb6j3DqqwHxMvNvC fQ4xut2KckbHuLgT4ejAPWDUYxJVqZpgjO2eYVTk9RRTXs9r4bX3nOZ0RGrt3PzeAjOg bsIUFwmdMlFFgAFvowUE5/t9I+t7NiTKN1qWYvOiIvI9hY+WR/yWnaWZdYhblLUwp2hE 302DP5k66IKZe1uC+uvZEFeDP1uaFiMbjatKLlQjpKAfsDZ/6yQDz4gMmwX6eRjDAlGE VLcFFRrHK3VU39q3FEWLhYpwkhcSsmx471m0SEYI19c6Wkity6z5qvNzK3CqVCQ9LlUy CiHQ== X-Gm-Message-State: AOJu0YzXsLltaUF2Leq2q4zq9UVFB31bIe5ND/n3XEKc6vHHhQLuDUGg oVIR+d/vyao4uvW1LAefdWUcMt8DqKrqyf3quTQ= X-Google-Smtp-Source: AGHT+IFXAv4GZ8rEMa4RackIQhVOIn0MPmwBFRqEVLUgEds99dhmstLz+PjV0u2Fwb94bs4dh4r4W6yYZQ7jTGE5OaM= X-Received: by 2002:a05:6820:228b:b0:56c:d297:164c with SMTP id ck11-20020a056820228b00b0056cd297164cmr6681058oob.4.1700920965448; Sat, 25 Nov 2023 06:02:45 -0800 (PST) MIME-Version: 1.0 Received: by 2002:ac9:7f50:0:b0:4f6:384b:17ef with HTTP; Sat, 25 Nov 2023 06:02:44 -0800 (PST) In-Reply-To: References: From: "David G. Johnston" Date: Sat, 25 Nov 2023 07:02:44 -0700 Message-ID: Subject: Re: reporting tree into separate columns To: Ibrahim Shaame Cc: Didier Gasser-Morlay , "pgsql-novice@lists.postgresql.org" Content-Type: multipart/alternative; boundary="000000000000efc885060afa852c" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000efc885060afa852c Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Saturday, November 25, 2023, Ibrahim Shaame wrote: > Thank you Didier for the response. But I can't see the solution there you > propose would give me the same thing (jina). Remember that the column > "jina" was obtained as a result of displaying a family tree. Now what I > would like is break out this column into a number of columns depending on > the depth. > > Any suggestions? > Pull the data into your langauge of choice and build out the presentation there. SQL doesn=E2=80=99t do dynamic columns from data very well. David J. --000000000000efc885060afa852c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Saturday, November 25, 2023, Ibrahim Shaame <ishaame@gmail.com> wrote:
Thank you Didier for the response. But I can'= ;t see the solution there you propose would give me the same thing (jina). = Remember that the column "jina" was obtained as a result of displ= aying a family tree. Now what I would like is break out this column into a = number of columns depending on the depth.

Any sugg= estions?

Pull the data into you= r langauge of choice and build out the presentation there.=C2=A0 SQL doesn= =E2=80=99t do dynamic columns from data very well.

David J.

=C2=A0
--000000000000efc885060afa852c--