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

From: Murtuza Zabuawala <murtuza(dot)zabuawala(at)enterprisedb(dot)com>
To: pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>
Subject: PATCH: To fix the issue in exclusion constraint (pgAdmin4)
Date: 2016-12-30 09:47:39
Message-ID: CAKKotZQ63rD_KTCXRhXJrOk2PHUbBEdzg3wi9_YPffZS+a+BZg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

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

--
Regards,
Murtuza Zabuawala
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Attachment Content-Type Size
RM_1896.patch application/octet-stream 5.1 KB

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message Khushboo Vashi 2016-12-30 10:10:41 [pgAdmin4][Patch]: RM 2006 - cannot modify table name or set schema on tables with postgis geometry column
Previous Message Surinder Kumar 2016-12-30 09:47:31 [pgAdmin4][Patch]: RM1832 - Dependency information not displayed for Synonym node