From: | Khushboo Vashi <khushboo(dot)vashi(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]: Fixed RM #2779 - Lost field size |
Date: | 2017-12-11 12:33:58 |
Message-ID: | CAFOhELcicZguE2m+iu1wTf=uj1R1DCCnXqfokrJdYTjUKKyvhA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
On Mon, Dec 11, 2017 at 5:45 PM, Khushboo Vashi <
khushboo(dot)vashi(at)enterprisedb(dot)com> wrote:
>
>
> On Mon, Dec 11, 2017 at 5:40 PM, Dave Page <dpage(at)pgadmin(dot)org> wrote:
>
>> Hi
>>
>> On Wed, Dec 6, 2017 at 5:45 AM, Khushboo Vashi <
>> khushboo(dot)vashi(at)enterprisedb(dot)com> wrote:
>>
>>> Hi,
>>>
>>> Please find the attached patch to fix RM #2779: Lost field size.
>>>
>>> While editing the table column, if we change collate then, the length
>>> and the precision are lost.
>>> Also, while changing column type, it does not honour the length and
>>> precision.
>>>
>>
>> Now it loses the collation if you edit the length.
>>
>> I have tested it, it's not loosing the collation.
> Please let me know the steps to reproduce this.
>
Reproduced. Will send the patch.
> :-(
>>
>>
> --
>> Dave Page
>> Blog: http://pgsnake.blogspot.com
>> Twitter: @pgsnake
>>
>> EnterpriseDB UK: http://www.enterprisedb.com
>> The Enterprise PostgreSQL Company
>>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Khushboo Vashi | 2017-12-11 12:46:01 | Re: [pgAdmin4][Patch]: Fixed RM #2779 - Lost field size |
Previous Message | Khushboo Vashi | 2017-12-11 12:15:52 | Re: [pgAdmin4][Patch]: Fixed RM #2779 - Lost field size |