From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | tarmo sepp <tarmosepp(dot)sepp(at)gmail(dot)com> |
Cc: | pgAdmin Support <pgadmin-support(at)postgresql(dot)org> |
Subject: | Re: Future of "Apply" button |
Date: | 2014-01-06 09:02:29 |
Message-ID: | CA+OCxowbjD4ODdjZgcMbHO+W49Qa5+-SaG186UfBmgYBmC5Gag@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
On Mon, Jan 6, 2014 at 7:33 AM, tarmo sepp <tarmosepp(dot)sepp(at)gmail(dot)com> wrote:
> Is there any hope to get back "Apply" button at least for functions?
Not unless someone writes a good, clean reliable implementation, which
seems unlikely.
> After
> removal of this button my productivity decreased significantly. It was very
> convenient to apply changes and to check result in real time. Especially
> when you're programming mostly stored functions and some of the functions
> are very long.
>
> I my case there are around 1100 functions and average length is 150 lines.
> IMHO buggy "Apply" button was much better than no button at all.
We've discouraged the use of the properties dialogue for that purpose
for many years - there's even a Guru Hint that tells you not to use
them that way. You should use the "CREATE SCRIPT" option on a
function, and edit it using the query tool which gives you much more
advanced editing features.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Steve Erickson | 2014-01-06 17:27:39 | Autovacuum ro prevent wraparound |
Previous Message | tarmo sepp | 2014-01-06 07:33:55 | Future of "Apply" button |