pgAdmin 4 v1.6 bug report

From: Jean Loesch <jean(dot)loesch(at)gmail(dot)com>
To: pgadmin-support(at)lists(dot)postgresql(dot)org
Subject: pgAdmin 4 v1.6 bug report
Date: 2017-07-28 08:54:39
Message-ID: CAGjW1O=gKip8zJNgqNcCv9Tw9PV=fN5uRJBgLybM9Be2+cvQUg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

Good morning,

The version of pgAdmin used is :
Version1.6
CopyrightCopyright 2013 - 2017, The pgAdmin Development Team
Python Version2.7.13 (v2.7.13:a06454b1afa1, Dec 17 2016, 20:42:59) [MSC
v.1500 32 bit (Intel)]
Flask Version0.11.1
Application ModeDesktop
Current Userpgadmin4(at)pgadmin(dot)org

The version of my postgres server is 9.3.4.
When I click on my database to get its DDL, it shows :
CREATE DATABASE area
WITH
OWNER = admarea
ENCODING = 'UTF8'
LC_COLLATE = 'en_US.UTF-8'
LC_CTYPE = 'en_US.UTF-8'
TABLESPACE = pg_default
CONNECTION LIMIT = -1;

ALTER DATABASE area
SET search_path TO '"$user", public, topology';

I have never quoted the search_path when I altered the database.

Now I drop my database and create it using DDL returned by pg_admin.
Then, objects in topology schema could not be found.

If I delete the quotes surrounding the search_path, objects in topology
schema could be found.

So pgAdmin seems to quote the search_path by error.

Regards.

Browse pgadmin-support by date

  From Date Subject
Next Message Derek Ealy 2017-07-31 16:30:33 error loading script after updating to 1.6
Previous Message Alex Ignatov 2017-07-27 12:17:30 RE: unsubscribe