Re: PATCH: To fix the issue in exclusion constraint (pgAdmin4)

From: Dave Page <dpage(at)pgadmin(dot)org>
To: Murtuza Zabuawala <murtuza(dot)zabuawala(at)enterprisedb(dot)com>
Cc: pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: PATCH: To fix the issue in exclusion constraint (pgAdmin4)
Date: 2017-01-08 13:43:37
Message-ID: CA+OCxow1ge+nvaMA6RB6XoJb2RL-Txnm5AMmsSb4Y8bYMRYa_Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

Hi

On Friday, December 30, 2016, Murtuza Zabuawala <
murtuza(dot)zabuawala(at)enterprisedb(dot)com> wrote:

> Hi,
>
> PFA patch to fix the issue where we were fetching wrong OID while
> generating node which was causing "index out of range". error when user
> try to access that exclusion constraint .
> RM#1896
>

I can't reproduce this, even following the steps in the ticket. How did you
manage to reproduce it?

--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message Harshal Dhumal 2017-01-09 07:10:59 Fwd: Patch for RM1911 Direct file navigation [pgAdmin4] [Feature]
Previous Message Dave Page 2017-01-08 13:35:30 Re: [pgAdmin4][patch]: RM #1745 - Fixed Clear breakpoint issue