Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sdQZe-00FRMv-4P for pgadmin-hackers@arkaria.postgresql.org; Mon, 12 Aug 2024 08:38:42 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sdQZc-00ECuN-PZ for pgadmin-hackers@arkaria.postgresql.org; Mon, 12 Aug 2024 08:38:40 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sdQZc-00ECuE-Ga for pgadmin-hackers@lists.postgresql.org; Mon, 12 Aug 2024 08:38:40 +0000 Received: from mail-lf1-x129.google.com ([2a00:1450:4864:20::129]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sdQZZ-004QUZ-SP for pgadmin-hackers@postgresql.org; Mon, 12 Aug 2024 08:38:39 +0000 Received: by mail-lf1-x129.google.com with SMTP id 2adb3069b0e04-52f01afa11cso4956864e87.0 for ; Mon, 12 Aug 2024 01:38:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pgadmin.org; s=google; t=1723451915; x=1724056715; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=NCIsFPa/N720RXsCV0kDnvSczlGVJ4pOXE+FHPeS278=; b=OsUUUD3CNH+psrKXA520dBQW51okDweMJSkUEfjxvyzTKXscinutl8qBEZJd14xoGk HYF/z+bihtCruZM7x6Piv1vX7CMemwgbhUIyHIyZ/pObpniQquQI9G+kgP7Thu9J+fC8 kAnSMKg/jz00DgpJCY1pexQt9Zx/67MbN5XvwzvA1jHKS1Z0kxRWWbE2zRrzEFBhmVvW z8tu8T3nAmHAj39KbOEzr011aTwK244l1JAbLVUFIQC3rfrOF7tZ+3E8d9wOUTbkMl29 keKeDdK3RAudtgNgPtWCiPHOG40VAvaMA2BncEZOfs+fwd8NKy/XOSy26wTzv7n8dpOg LndQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1723451915; x=1724056715; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=NCIsFPa/N720RXsCV0kDnvSczlGVJ4pOXE+FHPeS278=; b=w9Qc+cUKWReNJaD8K7DxBGZ3dUOdMfGbOy4J5nF3Ult+U+zE4wr/8Y28B83WVey9dP u+il3M/bcyanr2yKEVtfRxGk82W8ya+mTfWuZtE7X4jO+WgpnVhEIquTf7wECN4F1XvX rUcBgw18tUuMUJArYw0CJ5TkJL7W5TmnGXjUxg0e+nAOADf3qTeID8F484dMWhATlFXZ PEfz416JeIMji84s7pwloEL4pECKbS6XNW9y2IwHurBfI1ZIXCZDB9425CQXtYMdC2aK KM8S8P3uJ6jseTmEL/QlivccfSynF915PxPdw2iBsVjh8XGCYXKk4GlDx5YhywWE6zXs ufUg== X-Gm-Message-State: AOJu0Yw7UhISIa68KIoC3j0+N9omyznBeNkiTVAED4z8/PnDNIYTbcoR wdgGQ519iIt0adwvjIAU71qM4s7XDRYdXzJ9rfQcysXaLH/l/sghCrexEDq4/YOMSyybbFJGhBE gu0HctlUfqVLzpotdM1PbHrrWYpts4n8yjr7L+A8SVbYzxFk= X-Google-Smtp-Source: AGHT+IEYa4tQnTPKiEmUvkoxPsz6lH+t/duA2k3ySiqZ3kHMTs0601XlYGF69i3H2Roz2I4G2riKn0DM0cDOm2n6ZnU= X-Received: by 2002:a05:6512:1055:b0:52e:9d6c:4462 with SMTP id 2adb3069b0e04-530ee982320mr5792867e87.23.1723451914854; Mon, 12 Aug 2024 01:38:34 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Dave Page Date: Mon, 12 Aug 2024 09:38:23 +0100 Message-ID: Subject: Re: Regarding feature #3319 To: Anil Sahoo Cc: pgadmin-hackers Content-Type: multipart/alternative; boundary="0000000000002c3d99061f786bdf" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000002c3d99061f786bdf Content-Type: text/plain; charset="UTF-8" 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. > > > 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, > > 1. Store the query tool panels and the list of connections present in > each query tool panel and the active connection > 2. Store the query that is written in the editor > 3. 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 Page pgAdmin: https://www.pgadmin.org PostgreSQL: https://www.postgresql.org EDB: https://www.enterprisedb.com PGDay UK 2024, 11th September, London: https://2024.pgday.uk/ --0000000000002c3d99061f786bdf Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi

On Mon, 12 Aug 2024 at 06:50, Anil Sahoo <anil.sahoo@enterprisedb.com>= ; wrote:

Hi Hackers,


This feature=C2=A0#3319, demands the Workspace and the Query tool panel to be saved before ex= iting the application and on restart it will show earlier opened panels.


We are already saving the Browser layout, Que= ry 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 implementa= tion will be done,

  1. Store the query tool panels and the list of = connections present in each query tool panel and the active connection
  2. Store the query that is written in the edito= r
  3. Store the contents of scratch pad
The main reason that this has never been work= ed 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 tha= t? I assume in a similar way to the warnings we give if a connection has to= be re-established?=C2=A0


We will use debouncing to store the workspace= data and all other data related to panels in the pgAdmin 4's configure= d database file. Through debouncing we will be able to call the API at cert= ain intervals of user interaction, and it will update the stored data relat= ed to workspace and all other panels.

OK.=C2=A0

--
Dave Page
PostgreSQL: https://www.postgresql.org=

PGDay UK 2024,= 11th September, London: https://2024.pgday.uk/

--0000000000002c3d99061f786bdf--