Thanks, applied.
On Fri, Mar 1, 2019 at 12:41 PM Murtuza Zabuawala <
murtuza.zabuaw...@enterprisedb.com> wrote:
> Hello Aditya,
>
> Yes, that is a better approach, PFA updated patch.
>
> Thanks,
> Murtuza
>
>
> On Fri, Mar 1, 2019 at 4:35 PM Dave Page wrote:
>
>> That's a good idea. Seems much m
Hello Aditya,
Yes, that is a better approach, PFA updated patch.
Thanks,
Murtuza
On Fri, Mar 1, 2019 at 4:35 PM Dave Page wrote:
> That's a good idea. Seems much more robust.
>
> On Fri, Mar 1, 2019 at 11:02 AM Aditya Toshniwal <
> aditya.toshni...@enterprisedb.com> wrote:
>
>> Hi Murtuza,
>>
That's a good idea. Seems much more robust.
On Fri, Mar 1, 2019 at 11:02 AM Aditya Toshniwal <
aditya.toshni...@enterprisedb.com> wrote:
> Hi Murtuza,
>
> I would suggest adding a new url param like "?fslash=12,15", which says
> where to put the forward slashes.
>
> So if server name is "PostgreS
Hi Murtuza,
I would suggest adding a new url param like "?fslash=12,15", which says
where to put the forward slashes.
So if server name is "PostgreSQL/11" - connecting to postgres database with
postgres username:
Old URL:
http://localhost:5005/datagrid/panel/3400871/true/postgres%2Fpostgres%40Pos
On Fri, Mar 1, 2019 at 3:44 PM Aditya Toshniwal <
aditya.toshni...@enterprisedb.com> wrote:
> Hi Murtuza,
>
> Will this work if server name contains - !PG! ?
>
No, it won't and it's a custom signature we can finalize it whatever team
thinks will work if the functionality is working properly.
>
Hi Murtuza,
Will this work if server name contains - !PG! ?
On Fri, Mar 1, 2019 at 12:18 PM Murtuza Zabuawala <
murtuza.zabuaw...@enterprisedb.com> wrote:
> Hello,
>
> PFA patch for the issue RM#3998. If the URL contains the forward slash
> value in the query tool title and if pgAdmin4 is behind
