| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | Michael Brown <mikeb(at)360replays(dot)com> |
| Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
| Subject: | Re: PGAdmin 4 1.0-rc1 bugs |
| Date: | 2016-09-13 08:14:16 |
| Message-ID: | CA+OCxoyaJ07_QdYrJrkB85v-gZUCohTvojhos5o45+Rg1owhNA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
Hi
On Tue, Sep 13, 2016 at 3:11 AM, Michael Brown <mikeb(at)360replays(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashesh Vashi | 2016-09-13 08:32:19 | Re: PGAdmin 4 1.0-rc1 bugs |
| Previous Message | Murtuza Zabuawala | 2016-09-13 08:03:42 | PATCH: To fix the issue of Table node (pgAdmin4) |