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 1sfvbE-00DN4m-FK for pgadmin-hackers@arkaria.postgresql.org; Mon, 19 Aug 2024 06:10:40 +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 1sfvbC-00FfL2-Cx for pgadmin-hackers@arkaria.postgresql.org; Mon, 19 Aug 2024 06:10:39 +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 1sfvbC-00FfKu-2O for pgadmin-hackers@lists.postgresql.org; Mon, 19 Aug 2024 06:10:38 +0000 Received: from mail-oa1-x2f.google.com ([2001:4860:4864:20::2f]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sfvb8-000OIB-A1 for pgadmin-hackers@postgresql.org; Mon, 19 Aug 2024 06:10:37 +0000 Received: by mail-oa1-x2f.google.com with SMTP id 586e51a60fabf-268a9645e72so2739380fac.1 for ; Sun, 18 Aug 2024 23:10:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb.com; s=google; t=1724047833; x=1724652633; 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=CDFgRM0IVe+lwxuwLDFcJ9hXZ4CwrdESp/W5GV9Zvi8=; b=TuaHPU6VRvzqcUY9XNsm6gFYij5T7Vruxn1WQXuMryKgqbrR9VarP2kNZPWsIoCiIp J8UNdK0eD9MPUsaGYzpTOG0I12wY2blMUpXsxDcFttevkqmVqDdyGcjmytzvVbYQw4FA K2GgOZov4mYh4L9yRxg3J9H/Z4F9wQWAfcl24u+EFO06JtXOjvs7e7tIp6g23iZ2JaaQ 9X4EKNEDYIfXbpx9IkqYMIjSt6NF5goiWZLRWh9s+vWIrqME7JzVoHZBmV7B1c2stf7k Yx2TGSouWyEg5iApfTxIAOarfzFvGT7AjfCAUmF3KFlptkeow1uoIdBpmN3i+Iphd6vk u8Mg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1724047833; x=1724652633; 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=CDFgRM0IVe+lwxuwLDFcJ9hXZ4CwrdESp/W5GV9Zvi8=; b=EUbUHj9o4wcpjJ31946K4BiDobr4o47VPx5Jyr7i0tDjTgJYXgX6a8x0gUsLDeTFsQ NQqZ/uLgxP0hjhkzdPhUfb+g0/Z+W4mHdplrJXNGy+oDyqUd2z8/uUiaAd9TdsGIH2GD VoZH9HlJ9o+BsZH9NSRAb6A/qKU2UE/Pq3lMsGLpyR1MIbM+/kkzH+s5P6SBT33tupzF foOUU6bvyeyoN63hP7zK8WD2dEes98XsBixShRFmwiDGS1ILSIUMbU3LonSNGsnBNxKA mcYDM3fjyfd9rs0CB1ZB4TR9JcQ2PA8akb6j7vQ1nNkS5sHCrvROMLZFx/j6hHaHsrPE Entw== X-Forwarded-Encrypted: i=1; AJvYcCV4EkWlRo4d/Ll2Mffsezv+It6EODFd48iwC8TgdRSMHlSndDokCjCSZvfxaik/omyBrsearI6nFyds2SuLu8DqW58AbmQXMNji7MfoNqU= X-Gm-Message-State: AOJu0Yz3O8sffIdR6v5Uuk2qLgAHV3fmE12mHxXvY3cL9izMbLuY9gS8 zMqz7gZ01WjCkt5vCkyPj0QYXcc5Nd3gFBfApwRdqoVU0aKsPe6zuPK/No4/X9Nmn8klzg5Leu7 zH0YpegZLyWUjod0qpP8cF6qsXVPHHebHl76l X-Google-Smtp-Source: AGHT+IG4n0cwgejFRde+mmuMIuEYrbjNNWB7MGa8NBllG247dmUU/sAwelSrjCLwgk4unmSylUkX0j77x6XkblkoRrg= X-Received: by 2002:a05:6870:c18e:b0:261:1600:b1eb with SMTP id 586e51a60fabf-2701c5a0f1amr11771170fac.31.1724047832722; Sun, 18 Aug 2024 23:10:32 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Aditya Toshniwal Date: Mon, 19 Aug 2024 11:39:56 +0530 Message-ID: Subject: Re: Regarding feature #3319 To: Anil Sahoo Cc: Dave Page , pgadmin-hackers Content-Type: multipart/alternative; boundary="000000000000a54c0f0620032a34" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000a54c0f0620032a34 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Anil, On Mon, Aug 12, 2024 at 3:02=E2=80=AFPM 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 > -- > > > > *Anil Sahoo* > > Software Engineer > > www.enterprisedb.com > > Power to Postgres > > > > > > > > On Mon, Aug 12, 2024 at 2:08=E2=80=AFPM Dave Page wro= te: > >> 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 exiti= ng >>> 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 d= one, >>> >>> 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'v= e >> got it right. How do you propose to handle that? I assume in a similar w= ay >> 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 an= d >>> 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/ >> >> --=20 Thanks, Aditya Toshniwal pgAdmin Hacker | Sr. Software Architect | *enterprisedb.com* "Don't Complain about Heat, Plant a TREE" --000000000000a54c0f0620032a34 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi=C2=A0Anil,

On Mon, Aug 12, 2024 at 3:0= 2=E2=80=AFPM Anil Sahoo <= anil.sahoo@enterprisedb.com> wrote:
Hi,

Yes, We will store t= he details that are needed to re-establish the connection.

How/Where are you planning=C2=A0to store the information? Query= text could be large.

Regards
Anil
--
=

Anil Sahoo=

Software Engineer

www.enterp= risedb.com

Power to Postgres

=

=C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 <= /span> =C2=A0 =C2= =A0



On Mon, Aug 12, 2024 at 2:08=E2=80=AFPM Dave Page <dpage@pgadmin.org>= ; wrote:
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 Wor= kspace 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 init= ially 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&= #39;ve got it right. How do you propose to handle that? I assume in a simil= ar 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 da= ta related to panels in the pgAdmin 4's configured database file. Throu= gh 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 al= l other panels.


OK.=C2=A0<= /div>

-- =
Dave PagepgAdmin: https://w= ww.pgadmin.org
PostgreSQL: https://www.postgresql.org

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



--
Thanks,
Aditya Toshniwal
pgAdmin Hacker=C2=A0| Sr. Software Architect=C2=A0| enterprisedb.com