Re: Regarding feature #3319

Hi Dave, Yes, we can store connection info. We might need to tweak how we create the query tool connections. Thanks for the inputs. Thanks, Yogesh Mahajan EnterpriseDB On Thu, Mar 13, 2025 at 5:07 PM Dave Page wrote: > Hi > > On Thu, 13 Mar 2025 at 11:35, Yogesh Mahajan < > yogesh.maha...@ent

Re: Regarding feature #3319

Hi On Thu, 13 Mar 2025 at 11:35, Yogesh Mahajan < yogesh.maha...@enterprisedb.com> wrote: > Hi Dave, > > What about the query tools opened with an ad-hoc server, should we just > open a query tool with data without connections? > Can we not save the connection parameters used in the JSON (exclud

Re: Regarding feature #3319

Hi Dave, What about the query tools opened with an ad-hoc server, should we just open a query tool with data without connections? Thanks, Yogesh Mahajan EnterpriseDB On Thu, Mar 13, 2025 at 4:59 PM Dave Page wrote: > Hi > > On Thu, 13 Mar 2025 at 11:20, Yogesh Mahajan < > yogesh.maha...@enter

Re: Regarding feature #3319

Hi On Thu, 13 Mar 2025 at 11:20, Yogesh Mahajan < yogesh.maha...@enterprisedb.com> wrote: > Hi Dave, > > Couple of follow up questions - > > Thanks, > Yogesh Mahajan > EnterpriseDB > > > On Thu, Mar 13, 2025 at 4:37 PM Dave Page wrote: > >> >> >> On Tue, 11 Mar 2025 at 08:31, Yogesh Mahajan < >>

Re: Regarding feature #3319

Hi Dave, Couple of follow up questions - Thanks, Yogesh Mahajan EnterpriseDB On Thu, Mar 13, 2025 at 4:37 PM Dave Page wrote: > > > On Tue, 11 Mar 2025 at 08:31, Yogesh Mahajan < > yogesh.maha...@enterprisedb.com> wrote: > >> Hello Team, >> >> Couple of more questions arose during discussion

Re: Regarding feature #3319

On Tue, 11 Mar 2025 at 08:31, Yogesh Mahajan < yogesh.maha...@enterprisedb.com> wrote: > Hello Team, > > Couple of more questions arose during discussion - > > 1.What all tools should we reopen while restoration? It could be Query > tool, ERD, Psql, Schema diff as of now may get additional in futu

Re: Regarding feature #3319

Hello Team, Couple of more questions arose during discussion - 1.What all tools should we reopen while restoration? It could be Query tool, ERD, Psql, Schema diff as of now may get additional in future. 2.Can we use an existing crypt key to encrypt the query data or simply json encoding should be

Re: Regarding feature #3319

On Thu, 20 Feb 2025 at 10:56, Aditya Toshniwal < aditya.toshni...@enterprisedb.com> wrote: > Hi Dave, > > On Thu, Feb 20, 2025 at 3:22 PM Dave Page wrote: > >> >> >> On Thu, 20 Feb 2025 at 03:52, Aditya Toshniwal < >> aditya.toshni...@enterprisedb.com> wrote: >> >>> Hi Dave, >>> >>> On Wed, Feb 1

Re: Regarding feature #3319

Hi Dave, On Thu, Feb 20, 2025 at 3:22 PM Dave Page wrote: > > > On Thu, 20 Feb 2025 at 03:52, Aditya Toshniwal < > aditya.toshni...@enterprisedb.com> wrote: > >> Hi Dave, >> >> On Wed, Feb 19, 2025 at 6:55 PM Dave Page wrote: >> >>> >>> >>> On Wed, 19 Feb 2025 at 12:24, Yogesh Mahajan < >>> yog

Re: Regarding feature #3319

On Thu, 20 Feb 2025 at 03:52, Aditya Toshniwal < aditya.toshni...@enterprisedb.com> wrote: > Hi Dave, > > On Wed, Feb 19, 2025 at 6:55 PM Dave Page wrote: > >> >> >> On Wed, 19 Feb 2025 at 12:24, Yogesh Mahajan < >> yogesh.maha...@enterprisedb.com> wrote: >> >>> >>> Hi, >>> >>> On Wed, Feb 19, 20

Re: Regarding feature #3319

Hi Dave, On Wed, Feb 19, 2025 at 6:55 PM Dave Page wrote: > > > On Wed, 19 Feb 2025 at 12:24, Yogesh Mahajan < > yogesh.maha...@enterprisedb.com> wrote: > >> >> Hi, >> >> On Wed, Feb 19, 2025 at 5:12 PM Dave Page wrote: >> >>> Hi >>> >>> On Thu, 16 Jan 2025 at 06:37, Aditya Toshniwal < >>> adit

Re: Regarding feature #3319

> If I understand correctly, Users are complaining about losing unsaved data >> in the query tool and not about data output or session state. Hence just >> reopening the query tool with only data should be suffice. >> > > I'm sure that will suffice for 95%+ of users. The ones I'm concerned about >

Re: Regarding feature #3319

On Wed, 19 Feb 2025 at 12:24, Yogesh Mahajan < yogesh.maha...@enterprisedb.com> wrote: > > Hi, > > On Wed, Feb 19, 2025 at 5:12 PM Dave Page wrote: > >> Hi >> >> On Thu, 16 Jan 2025 at 06:37, Aditya Toshniwal < >> aditya.toshni...@enterprisedb.com> wrote: >> >>> Hi Anil/Dave, >>> >>> Why not use

Re: Regarding feature #3319

Hi, On Wed, Feb 19, 2025 at 5:12 PM Dave Page wrote: > Hi > > On Thu, 16 Jan 2025 at 06:37, Aditya Toshniwal < > aditya.toshni...@enterprisedb.com> wrote: > >> Hi Anil/Dave, >> >> Why not use browser localStorage for saving this information? It persists >> when the browser closes and is based on

Re: Regarding feature #3319

Hi On Thu, 16 Jan 2025 at 06:37, Aditya Toshniwal < aditya.toshni...@enterprisedb.com> wrote: > Hi Anil/Dave, > > Why not use browser localStorage for saving this information? It persists > when the browser closes and is based on the URL. It is safer to store at > the user's machine than on our s

Re: Regarding feature #3319

Hi Dave/Team, Here are 2 storage options - 1.IndexdDB - IndexdDB is supported by all the browsers except IE.(Ref ). Ele

Re: Regarding feature #3319

Hi Anil/Dave, Why not use browser localStorage for saving this information? It persists when the browser closes and is based on the URL. It is safer to store at the user's machine than on our server. For Electron also it should work. This will reduce load on the pgAdmin server. On Wed, Aug 28, 20

Re: Regarding feature #3319

Hi Hackers, We are going to store the below details 1. List of Query tools opened 2. List of connections present in each query tool 3. Each connection’s details that are required to make the connection once the application restarts 4. Active connection details of each query tool o

Re: Regarding feature #3319

Hi Anil, There can be multiple query tools open with large files. Not entirely sure if storing in SQLite DB is a good idea. External databases won't come in the picture as 99.99% users will not use external DB for desktop app. We're only doing this for desktop app. And also consider the case where

Re: Regarding feature #3319

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 --

Re: Regarding feature #3319

Hi Anil, On Mon, Aug 12, 2024 at 3:02 PM Anil Sahoo 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 > -- > > > >

Re: Regarding feature #3319

Hi, Yes, We will store the details that are needed to re-establish the connection. Regards Anil -- *Anil Sahoo* Software Engineer www.enterprisedb.com Power to Postgres

Re: Regarding feature #3319

Hi On Mon, 12 Aug 2024 at 06:50, Anil Sahoo wrote: > 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. > > >

Regarding feature #3319

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