Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bjjEA-0004do-9F for pgadmin-hackers@arkaria.postgresql.org; Tue, 13 Sep 2016 08:38:02 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bjjE9-0004DZ-7s for pgadmin-hackers@arkaria.postgresql.org; Tue, 13 Sep 2016 08:38:01 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bjjE8-0004DR-PG for pgadmin-hackers@postgresql.org; Tue, 13 Sep 2016 08:38:00 +0000 Received: from mail-it0-x236.google.com ([2607:f8b0:4001:c0b::236]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1bjjE5-0000Ri-OE for pgadmin-hackers@postgresql.org; Tue, 13 Sep 2016 08:38:00 +0000 Received: by mail-it0-x236.google.com with SMTP id o3so28345681ita.1 for ; Tue, 13 Sep 2016 01:37:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=5jc0BlApZD26N5WOtcX0t16t0cnaU/wFgdmUmO2ti9c=; b=0RumJsMEvPQLb/SdtpL6QQN53GYzaUG284SFYoCKYK2gmnULDkvyNIKZFVkigWvbJ4 VsufFoz0uenx/rFJx5F+3EBjkc7W14QtjujIae2Z3ibye5q5qPmt7GeDsvsJ7RdVpvlT EeVnrtZLe3xa1BktZ+piUjmbfO0s9YzFn6FDQQRKWLkMHLT/uEkDpwSO6ZWS+oan5Lzu 4Z+OUstjfNWBPZgn5//XMB/N5Un4ZLxUlf+IZNDsRdCP9JIRZFW1h3jKRgyvus7v51mB 6a2CcL9uAKFV0T9je3fQG65MZncFHwtk660onUWx/onBnPgMGLEjTBWavCMTq4M3/++w 3Sjg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=5jc0BlApZD26N5WOtcX0t16t0cnaU/wFgdmUmO2ti9c=; b=dvUuVpsP4lUE94yH9F60DRRKosWwWmkDt48pel/HcrDPkAyxk0dST6ml2adcF/Y2h3 ebuYU3Uv/91Pcr3PS/8oKnQFh262D378DPs0p52CUCS6fZVbHYThhKuTGNrdRgrrC1NG 2mPjU122Sx/hiOaIVeJAAhJ6oHiiwmIGp6JveYPXfRn1vqCwA0vO4Vs2Ow2Wra8006rD Yi58V6qUj20WbdfxR8AlnqEyqCkAhJifX8Mv6uTnB/ApSU0/bZ4bBe561UbTBs/Kou38 LN/RI5f3tRb27jP2Quen/uja286PPZPhRD+piic1JBClAflSTRC9WGZcf468txNKR4Vd GBLQ== X-Gm-Message-State: AE9vXwM52HdsMQeI0MmVRgFFnUQdgTGxB2qpy6J2Pk8746Ar0+WKCYpzg6Apqlj/lk2pK8AlzsYu6cIkCy9Yhr1y X-Received: by 10.107.176.144 with SMTP id z138mr117064ioe.133.1473755876111; Tue, 13 Sep 2016 01:37:56 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.50.212 with HTTP; Tue, 13 Sep 2016 01:37:35 -0700 (PDT) In-Reply-To: References: From: Ashesh Vashi Date: Tue, 13 Sep 2016 14:07:35 +0530 Message-ID: Subject: Re: PGAdmin 4 1.0-rc1 bugs To: Michael Brown Cc: pgadmin-hackers , Dave Page Content-Type: multipart/alternative; boundary=001a11438ad47b758e053c5f8710 X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgadmin-hackers Precedence: bulk Sender: pgadmin-hackers-owner@postgresql.org --001a11438ad47b758e053c5f8710 Content-Type: text/plain; charset=UTF-8 On Tue, Sep 13, 2016 at 2:02 PM, Ashesh Vashi wrote: > On Tue, Sep 13, 2016 at 1:44 PM, Dave Page wrote: > >> Hi >> >> On Tue, Sep 13, 2016 at 3:11 AM, Michael Brown >> 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.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 (pgadmin-hackers@postgresql.org) >> To make changes to your subscription: >> http://www.postgresql.org/mailpref/pgadmin-hackers >> > > --001a11438ad47b758e053c5f8710 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

On Tue, Sep 13, 2016 at 2:02 PM, Ashesh Vashi <ashesh.vas= hi@enterprisedb.com> wrote:

=
On Tue, Sep 13, 2016 at 1:44 PM, Dave Page <dpage@pgadm= in.org> wrote:
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=
Can you please some more details?
The in= formation 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 b= ackend?

- What do you mean by crashed? (Did runtim= e crash?)

Please ex= plain the detailed observation, and expectation too.

--

Thanks & Regards,

Ashesh Vashi
EnterpriseDB INDIA:=C2=A0Enterprise PostgreSQL Company


http://www.linkedin.com/in/ashes= hvashi

<= div>
--
Thanks & Regards,

<= div>Ashesh Vashi=C2=A0

> 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= 9;s a
> behavior change.

Logged here: https://redmine.postgresql.org/is= sues/1687

> O/S: Windows 10 Professional 64 bit
>
> I can probably contribute fixes once I get some free runway, I'm n= ot
> 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-ha= ckers


--001a11438ad47b758e053c5f8710--