Re: [pgAdmin4][Patch] To fix the issue in Function, Procedure &Trigger Function modules
От | Murtuza Zabuawala |
---|---|
Тема | Re: [pgAdmin4][Patch] To fix the issue in Function, Procedure &Trigger Function modules |
Дата | |
Msg-id | CAKKotZTt2W+w4_ra_Mm=MdSX=Vu3WOmmvZuYOQAF1bLS5k=_aw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [pgAdmin4][Patch] To fix the issue in Function, Procedure &Trigger Function modules (Dave Page <dpage@pgadmin.org>) |
Ответы |
Re: [pgAdmin4][Patch] To fix the issue in Function, Procedure &Trigger Function modules
|
Список | pgadmin-hackers |
Sorry, I think my last statement was misleading.
--
Regards,
On Thu, Jul 6, 2017 at 6:37 PM, Dave Page <dpage@pgadmin.org> wrote:
Maybe, but it's pretty clearly broken, so whilst you're fixing the template for that value, it would make sense to fix the UI too :-)On Thu, Jul 6, 2017 at 1:42 PM, Murtuza Zabuawala <murtuza.zabuawala@enterprisedb.com> wrote: Hi Dave,This behaviour is from beginning I think and it is inherited from pgAdmin3.--Regards,On Thu, Jul 6, 2017 at 5:58 PM, Dave Page <dpage@pgadmin.org> wrote:HiOn Thu, Jul 6, 2017 at 12:04 PM, Murtuza Zabuawala <murtuza.zabuawala@enterprisedb.com> wrote: Hi,PFA patch to fix the issue in Function, Procedure & Trigger Function modules where user was not able to update object if user changes the code definition.RM#2537This still doesn't seem quite right - the Rows field seems to be always greyed out, so I cannot set it to test at all.--Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company--Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
В списке pgadmin-hackers по дате отправления: