MIME-Version: 1.0
References: 
 <CAO+oWtC0aHG_7D69OiHvjHfpt9fJt=Q0LhPu_2oLCD71c1QORw@mail.gmail.com>
 <CA+OCxoz=3WbRzir+sP9qba97Tn4YrRV0bq5CFcVNtFsNKZ+5Lw@mail.gmail.com>
 <CAO+oWtAS2D3G_+rTOn2iY0HJLkJMjr2D6WNui+X8jZ_CSGiT_w@mail.gmail.com>
 <CAM9w-_=Y4ht5P9-PeDz++Sk5EAKU9jKkvTTNBU+mQEzWo0BoPw@mail.gmail.com>
 <CAO+oWtDjAydE7p8XSj4pW3WnXtgdoB+vQxC5AxsfdTsaVBRwbw@mail.gmail.com>
 <CAM9w-_n-Uh=rvV6CTESUnoiiUaUa2vxao7SJBVrrv1E0uMWRpQ@mail.gmail.com>
 <CAO+oWtCjn=0QCdXU1eXUk_zGqEn_qWQDAmoOadNkZwiUT58Jfg@mail.gmail.com>
 <CAM9w-_=42-JBrLX=-SB_6GyWC7PO1-T8MhvYn5r0aQcyZ+xt0w@mail.gmail.com>
 <CA+OCxozyK0z=UF+V1ypLxh0kJxW=NsgEObKSiJ-CZGdRfH5_Tw@mail.gmail.com>
 <CAMa=N=PGM2e3k0Vs7P_0O2sgsvU5HO2PgJVF6jWDarjvE2EXQA@mail.gmail.com>
 <CA+OCxoyXBn+heMWc7Jg_b+sB=+KnTwcwGBYj2Tx8bzSNNqV8Uw@mail.gmail.com>
In-Reply-To: 
 <CA+OCxoyXBn+heMWc7Jg_b+sB=+KnTwcwGBYj2Tx8bzSNNqV8Uw@mail.gmail.com>
From: Anthony DeBarros <anthonymdebarros@gmail.com>
Date: Wed, 19 Feb 2025 08:41:08 -0500
Message-ID: 
 <CACJO+64dUmaUH+FY=ag=A5aPrc8QkZiRJKs111s9TcNMBfY3Lw@mail.gmail.com>
Subject: Re: Regarding feature #3319
To: Dave Page <dpage@pgadmin.org>
Cc: Yogesh Mahajan <yogesh.mahajan@enterprisedb.com>,
	Aditya Toshniwal <aditya.toshniwal@enterprisedb.com>,
	Anil Sahoo <anil.sahoo@enterprisedb.com>,
	pgadmin-hackers <pgadmin-hackers@postgresql.org>
Content-Type: multipart/alternative; boundary="0000000000003f3b99062e7eeb82"
Archived-At: 
 <https://www.postgresql.org/message-id/CACJO%2B64dUmaUH%2BFY%3Dag%3DA5aPrc8QkZiRJKs111s9TcNMBfY3Lw%40mail.gmail.com>
Precedence: bulk

--0000000000003f3b99062e7eeb82
Content-Type: text/plain; charset="UTF-8"

> 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
> are those who (for example) have done SET search_path = ... and then
> performed some destructive operation that worked as expected because of the
> earlier SET, but might cause data loss or unexpected consequences if run
> without the SET.
>
> Granted, that class of issues is likely to affect only a small number of
> users in reality, but the consequences could easily be data loss.
>
>

Just a thought from an onlooker. My main request for this feature would be
to re-open query tool tabs with the contents restored, whether I had saved
the files or not. I don't think I would expect to see any results populated
in the results grid, nor would I expect temporary SET operations to also be
restored.

I am curious about a comment about saving data on the pgAdmin server. Would
that mean sending the contents of my files to a server outside my org?
Forgive me if I am misunderstanding.

Thanks,
Anthony

--0000000000003f3b99062e7eeb82
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_quote gmail_quote_container"><div><br>=
</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0p=
x 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><d=
iv dir=3D"ltr"><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote"=
 style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);p=
adding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_quote"><div></div><di=
v style=3D"font-family:verdana,sans-serif;font-size:small">If I understand =
correctly, Users are complaining=C2=A0about losing unsaved data in the quer=
y tool and not about data output or session state. Hence just reopening the=
 query tool with only data should be=C2=A0<span role=3D"heading" style=3D"c=
olor:rgb(0,0,0)">suffice</span>.</div></div></div></blockquote><div><br></d=
iv><div>I&#39;m sure that will suffice for 95%+ of users. The ones I&#39;m =
concerned about are those who (for example) have done SET search_path =3D .=
.. and then performed some destructive operation that worked as expected be=
cause of the earlier SET, but might cause data loss or unexpected consequen=
ces if run without the SET.</div><div><br></div><div>Granted, that class of=
 issues is likely to affect only a small number of users in reality, but th=
e consequences could easily be data loss.</div><div>=C2=A0</div></div></div=
></blockquote><div><br></div><div>Just a thought from an onlooker. My main =
request for this feature would be to re-open query tool tabs with the conte=
nts restored, whether I had saved the files or not. I don&#39;t think I wou=
ld expect to see any results populated in the results grid, nor would I exp=
ect temporary SET operations to also be restored.=C2=A0</div><div><br></div=
><div>I am curious about a comment about saving data on the pgAdmin server.=
 Would that mean sending the contents of my files to a server outside my or=
g? Forgive me if I am misunderstanding.</div><div><br></div><div>Thanks,</d=
iv><div>Anthony=C2=A0</div></div></div>

--0000000000003f3b99062e7eeb82--