From: | Alex Williams <valenceshell(at)protonmail(dot)com> |
---|---|
To: | Pgadmin Support <pgadmin-support(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Extra Paranthesis on joins on saving a view |
Date: | 2020-12-03 01:44:02 |
Message-ID: | Nbj9R0r1slYSqSlEy-MERv8hGPjQKMUUFZHbJp4CX2bp0_olYjLfYxx6-QImmQYvrBAwfWfFu-Q6-hBQhKWzngvHqqft8w8SMGQVyEFfzEk=@protonmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
Hi,
I'm not sure if this is something new but in previous versions of pgadmin (currently using 4.27 where this is happening,) when creating a view, more or less, my original sql was maintained, but now it's mangling the joins like MS Access does with the Jet database with lots of parenthesis's (yes, I still use Access 2000.) Is there a way to disable this? I find it very difficult to parse and wind up removing them all only to have come back when saved when I'm done modifying / saving the view.
Also, can you:
1. Allow renaming tables/functions/etc... without having to invoke properties....it's very slow sometimes to bring up that dialog....and sometimes I use rename just to copy a object name, not to rename it.
2. When running View/Edit->First 100 Rows, can you not lock it, i.e., it's a convenient way to have the select statement written without typing and then you add the predicates/joins.
3. When creating a table, can you please allow rearranging of the columns.
Thanks,
Alex
From | Date | Subject | |
---|---|---|---|
Next Message | Aditya Toshniwal | 2020-12-03 05:50:18 | Re: Extra Paranthesis on joins on saving a view |
Previous Message | Dave Page | 2020-12-02 13:15:44 | Re: [External] Re: pgadmin--pgagent---the process hang by unknow reasons |