pgAdmin 4 commit: Fix issue where reverse engineered SQL was failing fo

From: Akshay Joshi <akshay(dot)joshi(at)enterprisedb(dot)com>
To: pgadmin-hackers(at)lists(dot)postgresql(dot)org
Subject: pgAdmin 4 commit: Fix issue where reverse engineered SQL was failing fo
Date: 2019-06-10 06:47:30
Message-ID: E1haE5a-0007AR-Sv@gothos.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

Fix issue where reverse engineered SQL was failing for foreign tables, if it had = in the options. Fixes #4171

Branch
------
master

Details
-------
https://git.postgresql.org/gitweb?p=pgadmin4.git;a=commitdiff;h=7ff85903e4fe95f4dd918152e2577d80b0c577e8
Author: Aditya Toshniwal <aditya(dot)toshniwal(at)enterprisedb(dot)com>

Modified Files
--------------
docs/en_US/release_notes_4_9.rst | 1 +
.../servers/databases/schemas/foreign_tables/__init__.py | 4 +++-
2 files changed, 4 insertions(+), 1 deletion(-)

Browse pgadmin-hackers by date

  From Date Subject
Next Message Akshay Joshi 2019-06-10 06:47:47 Re: [pgAdmin][RM4171] Can not display sql of foreign table when used character = in options
Previous Message Akshay Joshi 2019-06-10 06:23:48 Re: [pgAdmin][RM4253] create new column with default value