Hi,
This patch has caused another new issue (or regression).
Issue: Select2 control does not work in multi-select mode.
Node affected due to this are Primary key, unique key, and all other node
where we have used select2 control in multi-select mode.
Commit id:
Thanks, applied.
On Fri, Jun 24, 2016 at 12:24 PM, Murtuza Zabuawala
wrote:
> Hi,
>
> PFA patch to fix the issue RM#1292.
>
> Earlier patch was not handling spaces properly.
> e.g- If user creates any objects which has spaces in its name then it fails
> to
Hi,
PFA patch to fix the issue RM#1292.
Earlier patch was not handling spaces properly.
e.g- If user creates any objects which has spaces in its name then it fails
to parse it next time user select it.
--
Regards,
Murtuza Zabuawala
EnterpriseDB: http://www.enterprisedb.com
The Enterprise
Thanks, patch applied.
On Mon, Jun 20, 2016 at 2:56 PM, Sanket Mehta
wrote:
> Hi,
>
> PFA the revised patch to resolve this issue which consists the change in
> control formatter.
>
>
> Regards,
> Sanket Mehta
> Sr Software engineer
> Enterprisedb
>
> On Mon, Jun
Hi,
PFA the revised patch to resolve this issue which consists the change in
control formatter.
Regards,
Sanket Mehta
Sr Software engineer
Enterprisedb
On Mon, Jun 13, 2016 at 3:12 PM, wrote:
> Issue #1292 has been updated by Dave Page.
>
>- *Target version*
Hi,
This will not work, this is generic issue and not specific to database name
only, we need to do proper unescaping of special character for every object
name.
( eg: create a schema with name as 'test\’ not go to table node and try to
create table by selecting 'test\’ schema, it will fail
Hi,
I have resolved the issue and patch is attached with this mail.
Please review it and let me know in case any issues.
Regards,
Sanket Mehta
Sr Software engineer
Enterprisedb
On Mon, Jun 6, 2016 at 4:23 PM, wrote:
> Issue #1292 has been updated by Sanket Mehta.
>
>