From: | Murtuza Zabuawala <murtuza(dot)zabuawala(at)enterprisedb(dot)com> |
---|---|
To: | Dave Page <dpage(at)pgadmin(dot)org> |
Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: [pgAdmin4][Patch]: Fix the logic to extract the error in Query tool |
Date: | 2017-09-18 13:07:12 |
Message-ID: | CAKKotZSQ5DM4ED9B=nOHJU1cnznGUMZKGpukWvvn2A18dO95sg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Hi Dave,
PFA patch.
On Mon, Sep 18, 2017 at 4:34 PM, Dave Page <dpage(at)pgadmin(dot)org> wrote:
> Hi
>
> On Mon, Sep 18, 2017 at 10:54 AM, Murtuza Zabuawala <murtuza.zabuawala@
> enterprisedb.com> wrote:
>
>> Hi,
>>
>> PFA minor patch to fix the issue where logic to extract the error using
>> RegEX from error message was incorrect in Query tool(History tab).
>> RM#2700
>>
>
> Thanks - applied, but....
>
> - Could you please add some JS tests to ensure parseErrorMessage continues
> to work as it should.
>
Done
>
> - I'm not happy with the fact that we still display:
>
> can't execute an empty query ********** Error **********
>
> Can we not make that look more like a real error message? At the very
> least something like:
>
> Error: can't execute an empty query
>
Done
>
>
>>
>> Another minor issue which I observed on login page is that close button
>> on alert is little misaligned(screenshot attached).
>>
>>
> Also applied - thanks!
>
> --
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
>
> EnterpriseDB UK: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
Attachment | Content-Type | Size |
---|---|---|
add_testcases_history_tab.diff | text/plain | 2.9 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Harshal Dhumal | 2017-09-18 13:12:29 | Fix for Exception when the server is restarted [RM2713][pgAdmin4] |
Previous Message | Akshay Joshi | 2017-09-18 12:52:23 | [pgAdmin4][Patch] RM 2691 View data option is missing from pgAdmin4 2.0 version |