MIME-Version: 1.0
In-Reply-To: 
 <CAKTs_erBYYLsi1ynL6hy_q2TTOv5Bs_sHPBZWXj__9-3sFKkZA@mail.gmail.com>
References: 
 <CAKTs_erBYYLsi1ynL6hy_q2TTOv5Bs_sHPBZWXj__9-3sFKkZA@mail.gmail.com>
From: Dave Page <dpage@pgadmin.org>
Date: Tue, 13 Sep 2016 09:14:16 +0100
Message-ID: 
 <CA+OCxoyaJ07_QdYrJrkB85v-gZUCohTvojhos5o45+Rg1owhNA@mail.gmail.com>
Subject: Re: PGAdmin 4 1.0-rc1 bugs
To: Michael Brown <mikeb@360replays.com>
Cc: pgadmin-hackers <pgadmin-hackers@postgresql.org>
Content-Type: text/plain; charset=UTF-8
Precedence: bulk
Sender: pgadmin-hackers-owner@postgresql.org

Hi

On Tue, Sep 13, 2016 at 3:11 AM, Michael Brown <mikeb@360replays.com> wrote:
> Hey guys - I hope this is the right place to post bugs, if not yell at me
> (why aren't you guys using a bug tracker?)

We are: https://redmine.postgresql.org/projects/pgadmin4/issues

> Bug #1 - if a database is recreated in a different connection, pgAdmin will
> crash when trying to access the database. (pgAdmin3 also does this).

https://redmine.postgresql.org/issues/1688

> Bug #2 - Table columns are sorted alphabetically unlike pgAdmin3. This means
> determining INSERT order without specifying columns isn't possible without
> generating an INSERT script. This maybe should be preferenced as it's a
> behavior change.

Logged here: https://redmine.postgresql.org/issues/1687

> O/S: Windows 10 Professional 64 bit
>
> I can probably contribute fixes once I get some free runway, I'm not
> familiar with the codebase yet.

That would certainly be appreciated!

Thanks!

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

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


-- 
Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-hackers