From: | Michel Feinstein <michelfeinstein(at)gmail(dot)com> |
---|---|
To: | Michael Shapiro <mshapiro51(at)gmail(dot)com> |
Cc: | Dave Page <dpage(at)pgadmin(dot)org>, "Ray O'Donnell" <ray(at)rodonnell(dot)ie>, Pgadmin-Support <pgadmin-support(at)postgresql(dot)org> |
Subject: | Re: save SQL in PgAdmin4 |
Date: | 2019-07-18 14:44:37 |
Message-ID: | CAEg4jbM=eA1p7SMXPn0180Tb2ODMOV5UPiZBOgwed7UPMDUWwA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
In that case I would say you need a "Save as..." button, whereas the "Save"
button will track changes and only save if there are any changes.
On Thu, Jul 18, 2019, 11:42 Michael Shapiro <mshapiro51(at)gmail(dot)com> wrote:
> Dave,
>
> I'd like to make a feature request that PgAdmin4 add a save button (that
> is always enabled) to any window that displays SQL.
> Most editors I have worked with always provide a save (and/or save as)
> even if the text has not changed.
> Even PgAdmin3 has a Save button for SQL displayed in the SQL window.
>
> On Thu, Jul 18, 2019 at 9:22 AM Dave Page <dpage(at)pgadmin(dot)org> wrote:
>
>>
>>
>> On Thu, Jul 18, 2019 at 3:09 PM Ray O'Donnell <ray(at)rodonnell(dot)ie> wrote:
>>
>>> On 18/07/2019 14:43, Michael Shapiro wrote:
>>> > Then what?
>>> >
>>> > On Thu, Jul 18, 2019 at 8:31 AM Ray O'Donnell <ray(at)rodonnell(dot)ie
>>> > <mailto:ray(at)rodonnell(dot)ie>> wrote:
>>> >
>>> > On 18/07/2019 14:28, Michael Shapiro wrote:
>>> > > After selecting an object (eg a view) how do I save the SQL that
>>> > > PgAdmin4 extracts from the server? I don't see a "SAVE" button.
>>> > >
>>> >
>>> > Hi there,
>>> >
>>> > Right-click on it in the object tree (Left of screen), then select
>>> > Scripts -> (type of script required).
>>>
>>> [Please keep replies on-list, and avoid top-posting - thanks.]
>>>
>>> Now that you ask, that's a good question.... I just tried it myself
>>> (Scripts -> Create script), and the "Save" button is greyed out.
>>>
>>> You can activate it by making some small edit in the generated SQL, but
>>> this seems like a bug.
>>>
>>
>> Depends how you look at it. The button is looking for changes the user
>> has made, not pre populated or loaded text. It's like when you double-click
>> on a file and it opens in an editor - most will not enable the save button
>> at that point.
>>
>> --
>> Dave Page
>> Blog: http://pgsnake.blogspot.com
>> Twitter: @pgsnake
>>
>> EnterpriseDB UK: http://www.enterprisedb.com
>> The Enterprise PostgreSQL Company
>>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Shapiro | 2019-07-18 15:04:40 | Re: save SQL in PgAdmin4 |
Previous Message | Michael Shapiro | 2019-07-18 14:41:54 | Re: save SQL in PgAdmin4 |