Re: Regarding feature #3319 - Mailing list pgadmin-hackers
Hi Aditya,
As we are already storing the query history in the pgAdmin 4's database file.
I am planning to store the information the same way. That can be an internal database file like SQLite or external database.
Let me know if you all have any suggestions on this.
Thanks
Anil
--
On Mon, Aug 19, 2024 at 11:40 AM Aditya Toshniwal <aditya.toshniwal@enterprisedb.com> wrote:
Hi Anil,On Mon, Aug 12, 2024 at 3:02 PM Anil Sahoo <anil.sahoo@enterprisedb.com> wrote:Hi,
Yes, We will store the details that are needed to re-establish the connection.How/Where are you planning to store the information? Query text could be large.Regards
Anil--
Hi Hackers,
This feature #3319, demands the Workspace and the Query tool panel to be saved before exiting the application and on restart it will show earlier opened panels.
We are already saving the Browser layout, Query tool layout and the Object explorer tree state but to save the contents of panels we will initially start with the Query tool. The below implementation will be done,
- Store the query tool panels and the list of connections present in each query tool panel and the active connection
- Store the query that is written in the editor
- Store the contents of scratch pad
The main reason that this has never been worked on is that there is no way to restore the state of a connection to what it was and be sure we've got it right. How do you propose to handle that? I assume in a similar way to the warnings we give if a connection has to be re-established?
We will use debouncing to store the workspace data and all other data related to panels in the pgAdmin 4's configured database file. Through debouncing we will be able to call the API at certain intervals of user interaction, and it will update the stored data related to workspace and all other panels.
OK.--Dave PagepgAdmin: https://www.pgadmin.org--Thanks,Aditya Toshniwal"Don't Complain about Heat, Plant a TREE"
pgadmin-hackers by date: