Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l7XPj-0003Ha-Ut for pgadmin-hackers@arkaria.postgresql.org; Thu, 04 Feb 2021 05:42:48 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1l7XPi-0005XO-Sf for pgadmin-hackers@arkaria.postgresql.org; Thu, 04 Feb 2021 05:42:46 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l7XPi-0005XH-J7 for pgadmin-hackers@lists.postgresql.org; Thu, 04 Feb 2021 05:42:46 +0000 Received: from mail-lf1-x12c.google.com ([2a00:1450:4864:20::12c]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1l7XPf-0003Dw-2h for pgadmin-hackers@postgresql.org; Thu, 04 Feb 2021 05:42:46 +0000 Received: by mail-lf1-x12c.google.com with SMTP id i187so2760775lfd.4 for ; Wed, 03 Feb 2021 21:42:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=rSWJJrKe0BUzFNncQMtiA7T5acRh/no2e0ehRC6RtZ8=; b=UR9j6Nkm+KsjiCTeVjWAklFwOnffWiapQCl6kELXTwZIi9Gle478yM6HeHs9slUH93 1RgCjgs1mO8fHf+Tnr5Xq5tsl0JUcJv2pcI/lk0mFFTKl0YDNBUcbnH4Y1CM9VfCLO6U Xomw8JNC4eaxIJBfZSKsPWHQ9EAWHpcRm4J5lH7RIda7BIB8PmXXcHz6DWTSMevQja2u tLEp71jhtlPUDk1HpSJ9mlPnHliv++bhG0oJLI+qaX1k+mwGfoEZ78zzd510Fq+5nIlU vF3mavBO9nYrh4MTdaA26/5k6GeGmT5QOvWrXWMKjUbcyyiyNjXR4ELpohENGe6GuaiX O2Lg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=rSWJJrKe0BUzFNncQMtiA7T5acRh/no2e0ehRC6RtZ8=; b=D667Ni9MkwHugQ2v1oZ6AJUc/zsjym6gNVOwDkd9c34t15qgFyTdFHl7dj0IxR8+W2 yENdiWITSXHOgMbQ5OmhIcVQL+fA7uDp1qde1E2aksRWNKQ4GKpyUfEBLDegPnif/xIi UExgRcooC4/blkP4cmOnRBRFWV+e8mroCSv2hYLg4ogS1IKoJPARN2cY2ke4Wb9Z3wQk 9tAUST4xchRbWASdzK01+ZLHo3G2Tc/bQ2W79GNft3IM8TOm9xt5ZaCAXTcvaeb1RzbR x9ePNRBscI+Hnu2RWkGazE046syJug12NwwISqxHdM47YsqZXkkFg/M0mopBzOrs0Fr0 CJXw== X-Gm-Message-State: AOAM531252VrSnyKSn4JQzmcS3R20KPNQxwGmNWM/4escmHab4Nj/2UR i7kKm2alO6hNTYXOp7tjOYUtdmRm5JL3v1SKkSENJ5eAezCIYnulxIV7xhu224mslb0o5awxchQ 0z+TAzdGRUgJXTIgl0doTO79R0DkCbf0abP+pCEF092RByMn4vcGAsUQqcWNmcMfP3JgCKKMaC4 0jh+FgUfQbKERj3EyI9nulHUSPGZUTGaQ58Uv+kFzKhug9vLIms4dSnGAUjQ== X-Google-Smtp-Source: ABdhPJydX1FOUkMHyVcdQ6HnMVwC502WekRC02NHbJC1FFbddUaKkCWS35iRQuqsGmQp8LKTEMfIJpyp1622rIPPD1s= X-Received: by 2002:a05:6512:1284:: with SMTP id u4mr3783933lfs.175.1612417361482; Wed, 03 Feb 2021 21:42:41 -0800 (PST) MIME-Version: 1.0 References: <76C585AF-824C-4FD5-BF3A-43AEA7BA402F@gmail.com> In-Reply-To: <76C585AF-824C-4FD5-BF3A-43AEA7BA402F@gmail.com> From: Aditya Toshniwal Date: Thu, 4 Feb 2021 11:12:05 +0530 Message-ID: Subject: Re: pgAdmin: ERD Tool a suggestion. To: Hitesh Patel Cc: pgadmin-hackers Content-Type: multipart/alternative; boundary="0000000000000fac4305ba7c2c9a" X-CLOUD-SEC-AV-Info: enterprisedb,google_mail,monitor X-CLOUD-SEC-AV-Sent: true X-Gm-Spam: 0 X-Gm-Phishy: 0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --0000000000000fac4305ba7c2c9a Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Hitesh, On Wed, Feb 3, 2021 at 8:55 PM Hitesh Patel wrote: > Dear pgAdmin Hackers, > > I notice in the latest version of pgAdmin (4.30) there is a ERD beta tool= . > > I wanted to suggest a feature which would be most helpful for database > developers (not sure if you already working on this). > > A lot of times I need to propose changes to the database and the database > has 100s of table, which becomes very difficult to view altogether. > > What I was looking to suggest is to connect to an existing database, but > then be able to select existing =E2=80=98database table(s)=E2=80=99, with= the =E2=80=98ERD tool=E2=80=99 > then able to create all the links/attribute info in the view. So bit like > =E2=80=98Generate ERD, but allow me to choose/restrict the tables=E2=80= =99. This allows me > to generate =E2=80=98different perspectives=E2=80=99 of my database and f= ocus on the > functionality they deliver in discussion/proposals/documentation. > Can you please create a feature request here - https://redmine.postgresql.org/projects/pgadmin4/issues/new ? > > > Kinds Regards, > > Hitesh Patel > PS: very excited with this feature. > > > > --=20 Thanks, Aditya Toshniwal pgAdmin hacker | Sr. Software Engineer | *edbpostgres.com* "Don't Complain about Heat, Plant a TREE" --0000000000000fac4305ba7c2c9a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Hitesh,

On Wed, Feb 3, 2021 at 8:55 PM= Hitesh Patel <hds.hcp@gmail.com> wrote:
Dea= r pgAdmin Hackers,

I notice in the latest version of pgAdmin (4.30) there is a ERD beta tool. =

I wanted to suggest a feature which would be most helpful for database deve= lopers (not sure if you already working on this).

A lot of times I need to propose changes to the database and the database h= as 100s of table, which becomes very difficult to view altogether.

What I was looking to suggest is to connect to an existing database, but th= en be able to select existing =E2=80=98database table(s)=E2=80=99, with the= =E2=80=98ERD tool=E2=80=99 then able to create all the links/attribute inf= o in the view. So bit like =E2=80=98Generate ERD, but allow me to choose/re= strict the tables=E2=80=99. This allows me to generate =E2=80=98different p= erspectives=E2=80=99 of my database and focus on the functionality they del= iver in discussion/proposals/documentation.


Kinds Regards,

Hitesh Patel
PS: very excited with this feature.





--
Thanks,
Aditya Toshniwal
pgAdmin hacker=C2=A0| Sr. Softwa= re Engineer | edbpostgres.com<= /font>
"Don't Complain about Heat, Plant a TREE&qu= ot;
--0000000000000fac4305ba7c2c9a--