Aditya, Didier, Agreed, a preference, or a couple of options, would probably make the most sense. I think the following options should cover most cases:
- Limit to object dragged (current behavior) - Include immediate relationships ( 1 level ) - Include x relationships ( user configurable ) - Include all relationships ( may end up with the entire database, in hyper connected schema ) I hope that helps, rik. On Thu, Aug 18, 2022 at 1:28 AM Didier Gasser-Morlay <didie...@gmail.com> wrote: > May be limit the chain to one level, and revisit the dependencies tree at > each table dropped onto the ERD surface, > > On Thu, 18 Aug 2022 at 07:22, Aditya Toshniwal < > aditya.toshni...@enterprisedb.com> wrote: > >> Hi Richard, >> >> The only problem I see with this is a table can refer to one or more >> tables and the referred can refer to more tables and so on. >> But I think that can be made optional with a preference setting. >> >> On Wed, Aug 17, 2022 at 9:18 PM richard coleman < >> rcoleman.ascen...@gmail.com> wrote: >> >>> Aditya, >>> >>> How about an option to drag any/all related items when you drag one that >>> is tied to other elements? >>> >>> Just a thought. >>> rik. >>> >>> On Wed, Aug 17, 2022 at 5:33 AM Aditya Toshniwal < >>> aditya.toshni...@enterprisedb.com> wrote: >>> >>>> Hi Didier, >>>> >>>> Since we can drop one table at a time, it is not possible to keep >>>> relations without the referred table. >>>> One possible solution could be to drag the referred table first and >>>> then the referring table. But, this is not yet implemented. You can raise a >>>> feature request here >>>> https://redmine.postgresql.org/projects/pgadmin4/issues/new if you >>>> think this solution will do. >>>> >>>> >>>> On Wed, Aug 17, 2022 at 12:54 PM Didier Gasser-Morlay < >>>> didie...@gmail.com> wrote: >>>> >>>>> Hello all, >>>>> >>>>> Using PGAdmin 4 v 6.12 in desktop mode, and I am starting to use the >>>>> ERD tool and I have a question and a feature request (not too sure where >>>>> to >>>>> put this one) >>>>> >>>>> Question :Drag and drop tables from browser tree to the diagram : PK >>>>> are reverse engineered but FKs are left behind - How can I manage this? I >>>>> was hoping that by using drap/drop of several tables the links would >>>>> transfert over but I can't seem to multi select in the browser tree >>>>> >>>>> >>>>> Feature request : I would love to be able to display only table name/ >>>>> Primary key field and any field involved in a fk. when just showing / >>>>> explaining a database to a fellow worker showing just the relations & >>>>> relationships goes a long way to quickly grasp the workings of a db. And >>>>> it >>>>> also allows to have a compact view which printed serves as a reminder. >>>>> >>>>> Thanks for making and keeping PgAdmin the excellent product that it is >>>>> >>>>> Didier >>>>> >>>>> >>>>> >>>>> >>>>> >>>> >>>> -- >>>> Thanks, >>>> Aditya Toshniwal >>>> pgAdmin Hacker | Software Architect | *edbpostgres.com* >>>> <http://edbpostgres.com> >>>> "Don't Complain about Heat, Plant a TREE" >>>> >>> >> >> -- >> Thanks, >> Aditya Toshniwal >> pgAdmin Hacker | Software Architect | *edbpostgres.com* >> <http://edbpostgres.com> >> "Don't Complain about Heat, Plant a TREE" >> >
