public inbox for [email protected]help / color / mirror / Atom feed
PGAdmin 4 1.0-rc1 bugs 4+ messages / 3 participants [nested] [flat]
* PGAdmin 4 1.0-rc1 bugs @ 2016-09-13 02:11 Michael Brown <[email protected]> 0 siblings, 1 reply; 4+ messages in thread From: Michael Brown @ 2016-09-13 02:11 UTC (permalink / raw) To: pgadmin-hackers 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?) Bug #1 - if a database is recreated in a different connection, pgAdmin will crash when trying to access the database. (pgAdmin3 also does this). 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. 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. -Michael ^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: PGAdmin 4 1.0-rc1 bugs @ 2016-09-13 08:14 Dave Page <[email protected]> parent: Michael Brown <[email protected]> 0 siblings, 1 reply; 4+ messages in thread From: Dave Page @ 2016-09-13 08:14 UTC (permalink / raw) To: Michael Brown <[email protected]>; +Cc: pgadmin-hackers Hi On Tue, Sep 13, 2016 at 3:11 AM, Michael Brown <[email protected]> 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 ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-hackers ^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: PGAdmin 4 1.0-rc1 bugs @ 2016-09-13 08:32 Ashesh Vashi <[email protected]> parent: Dave Page <[email protected]> 0 siblings, 1 reply; 4+ messages in thread From: Ashesh Vashi @ 2016-09-13 08:32 UTC (permalink / raw) To: Michael Brown <[email protected]>; +Cc: pgadmin-hackers; Dave Page <[email protected]> On Tue, Sep 13, 2016 at 1:44 PM, Dave Page <[email protected]> wrote: > Hi > > On Tue, Sep 13, 2016 at 3:11 AM, Michael Brown <[email protected]> > 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 Can you please some more details? The information given is not good enough for understanding the exact issue. i.e. - Operating System - Python Version - Runtime/Web mode - What error are you getting in the backend? - What do you mean by crashed? (Did runtime crash?) -- Thanks & Regards, Ashesh Vashi > > > 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 ([email protected]) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgadmin-hackers > ^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: PGAdmin 4 1.0-rc1 bugs @ 2016-09-13 08:37 Ashesh Vashi <[email protected]> parent: Ashesh Vashi <[email protected]> 0 siblings, 0 replies; 4+ messages in thread From: Ashesh Vashi @ 2016-09-13 08:37 UTC (permalink / raw) To: Michael Brown <[email protected]>; +Cc: pgadmin-hackers; Dave Page <[email protected]> On Tue, Sep 13, 2016 at 2:02 PM, Ashesh Vashi <[email protected] > wrote: > On Tue, Sep 13, 2016 at 1:44 PM, Dave Page <[email protected]> wrote: > >> Hi >> >> On Tue, Sep 13, 2016 at 3:11 AM, Michael Brown <[email protected]> >> 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 > > Can you please some more details? > The information given is not good enough for understanding the exact issue. > > i.e. > - Operating System > - Python Version > - Runtime/Web mode > - What error are you getting in the backend? > > - What do you mean by crashed? (Did runtime crash?) > Please explain the detailed observation, and expectation too. -- Thanks & Regards, Ashesh Vashi EnterpriseDB INDIA: Enterprise PostgreSQL Company <http://www.enterprisedb.com/; *http://www.linkedin.com/in/asheshvashi* <http://www.linkedin.com/in/asheshvashi; > > -- > Thanks & Regards, > > Ashesh Vashi > >> >> > 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 ([email protected]) >> To make changes to your subscription: >> http://www.postgresql.org/mailpref/pgadmin-hackers >> > > ^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2016-09-13 08:37 UTC | newest] Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2016-09-13 02:11 PGAdmin 4 1.0-rc1 bugs Michael Brown <[email protected]> 2016-09-13 08:14 ` Dave Page <[email protected]> 2016-09-13 08:32 ` Ashesh Vashi <[email protected]> 2016-09-13 08:37 ` Ashesh Vashi <[email protected]>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox