public inbox for [email protected]
help / color / mirror / Atom feedFrom: Ashesh Vashi <[email protected]>
To: Michael Brown <[email protected]>
Cc: pgadmin-hackers <[email protected]>
Cc: Dave Page <[email protected]>
Subject: Re: PGAdmin 4 1.0-rc1 bugs
Date: Tue, 13 Sep 2016 14:07:35 +0530
Message-ID: <CAG7mmowWR70QSNvs=-LqA5WY5znhZryuGLczoRbozb_jVXTACA@mail.gmail.com> (raw)
In-Reply-To: <CAG7mmoyTy26BewNN3ibDc_JjfyJ3JDk5c0833KJxoP7r28UMDw@mail.gmail.com>
References: <CAKTs_erBYYLsi1ynL6hy_q2TTOv5Bs_sHPBZWXj__9-3sFKkZA@mail.gmail.com>
<CA+OCxoyaJ07_QdYrJrkB85v-gZUCohTvojhos5o45+Rg1owhNA@mail.gmail.com>
<CAG7mmoyTy26BewNN3ibDc_JjfyJ3JDk5c0833KJxoP7r28UMDw@mail.gmail.com>
List-Unsubscribe: <mailto:[email protected]?body=unsub%20pgadmin-hackers>
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
>>
>
>
view thread (4+ messages)
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: PGAdmin 4 1.0-rc1 bugs
In-Reply-To: <CAG7mmowWR70QSNvs=-LqA5WY5znhZryuGLczoRbozb_jVXTACA@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox