From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
Cc: | Ashesh Vashi <ashesh(dot)vashi(at)enterprisedb(dot)com>, Timon <timosha(at)gmail(dot)com>, pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: error in last pgadmin git version |
Date: | 2010-08-19 09:46:02 |
Message-ID: | AANLkTik0pWWWm6M99UVJUr-HL9G56H6c16_0nHrMWjEn@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
On Thu, Aug 19, 2010 at 10:32 AM, Guillaume Lelarge
<guillaume(at)lelarge(dot)info> wrote:
> Le 19/08/2010 11:29, Dave Page a écrit :
>> On Thu, Aug 19, 2010 at 9:36 AM, Ashesh Vashi
>> <ashesh(dot)vashi(at)enterprisedb(dot)com> wrote:
>>> I am able to reproduce it (it is reproducible with an index constraints in
>>> the table.)
>>> And, also found one more crash while working on it.
>>> Steps to reproduce:
>>> - Create a table without any constraint
>>> i.e. CREATE TABLE xyz(c1 integer, c2 character varying);
>>> - Open Table Properties for the 'xyz' table.
>>> - Go to 'Constraints' tab
>>> - Click 'Add' button
>>> - It will open the 'New primary key' dialog
>>> - Go to 'Columns' tab
>>> - Select any column from the column combo-box and Boom... (Crashed).
>>
>> Works fine here. Can you debug at your end?
>>
>
> Probably Ashesh wasn't using your patch when he did his test?
Perhaps, but I don't see offhand how it would have affected the issue
he describes.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise Postgres Company
From | Date | Subject | |
---|---|---|---|
Next Message | Ashesh Vashi | 2010-08-19 10:02:01 | Re: error in last pgadmin git version |
Previous Message | Guillaume Lelarge | 2010-08-19 09:32:35 | Re: error in last pgadmin git version |