| From: | Khushboo Vashi <khushboo(dot)vashi(at)enterprisedb(dot)com> |
|---|---|
| To: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
| Subject: | Re: [pgAdmin4][Patch]: Fixed RM 1603 & RM 1220 |
| Date: | 2016-10-14 13:31:18 |
| Message-ID: | CAFOhELfRjpu04SnCLAJ+OvjYzwSjKKH-LWttdkRgu=wJbmipAQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
Hi,
The fix does not include a special case when database name has an equal to
(=) character in it.
Thanks,
Khushboo
On Fri, Oct 14, 2016 at 6:58 PM, Khushboo Vashi <
khushboo(dot)vashi(at)enterprisedb(dot)com> wrote:
> Hi,
>
> Please find the attached patch to fix the below 2 bugs.
>
> RM 1603: [Web Based] Export database failed if object contains double
> quotes.
> RM 1220: Backup database is not working with special characters
>
> The issues which were fixed:
>
> 1. Client side data were not unescaped
> 2. Required command line arguments were quoted twice
>
> Thanks,
> Khushboo
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Surinder Kumar | 2016-10-14 14:18:06 | [pgAdmin4][Patch]: SYNONYM issue if use all special characters as name |
| Previous Message | Khushboo Vashi | 2016-10-14 13:28:12 | [pgAdmin4][Patch]: Fixed RM 1603 & RM 1220 |