Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1ZmdoQ-0004hy-Dg for pgadmin-support@arkaria.postgresql.org; Thu, 15 Oct 2015 08:22:58 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1ZmdoP-0006y7-Sc for pgadmin-support@arkaria.postgresql.org; Thu, 15 Oct 2015 08:22:57 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1Zmdo0-0006X5-54 for pgadmin-support@postgresql.org; Thu, 15 Oct 2015 08:22:32 +0000 Received: from mail-lb0-f173.google.com ([209.85.217.173]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1Zmdnp-0000NS-47 for pgadmin-support@postgresql.org; Thu, 15 Oct 2015 08:22:30 +0000 Received: by lbwr8 with SMTP id r8so63194640lbw.2 for ; Thu, 15 Oct 2015 01:22:18 -0700 (PDT) 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:content-type; bh=THg9WlEubxoamg+CadI7dV/9wwJIwsCA+IsJzWyQFFM=; b=UvdzTzs0l+/IdVSAmS34mFpxxa6Tyoofq6gqcQYRaXC55bi04iX4YNhT7tn7m3SVQ6 BZ0U27iIixP1125pZtjbfiAfyXt77Uu8HkVhNF/p2gyB6D/iB0JX2H76D3QhTb1Y7g6V 8A1Wb/5+IgpYdFbjFd2tDuVA9kiYbSfPNvRTQxNbthQh1HDbPjo0/ukHHEh2OHjIzt7c erYQm/3Ufet/Jng6DzmUaQCYd9kgSYhe+k5o+79AtrlYpmqZHEkm3pieYI9EQT2C3xyh DjBcSM3plOVSWOvkNQ/cWCQd4dtYVxVWwwdpEVHcbvxNPa1K1FrxOgpSWJJFvraaSdNt bSrw== X-Gm-Message-State: ALoCoQkkx6PE8Gix/BpTRlgyE0Kn7P12g1nZ99/QMRs2yqZOAnqbsvqiYShvvaSPNWP5AyOftalH X-Received: by 10.112.184.196 with SMTP id ew4mr3766853lbc.17.1444897338428; Thu, 15 Oct 2015 01:22:18 -0700 (PDT) MIME-Version: 1.0 Received: by 10.112.181.37 with HTTP; Thu, 15 Oct 2015 01:21:58 -0700 (PDT) In-Reply-To: <1444887919111-5870044.post@n5.nabble.com> References: <1444887919111-5870044.post@n5.nabble.com> From: Ashesh Vashi Date: Thu, 15 Oct 2015 13:51:58 +0530 Message-ID: Subject: Re: Error about inherited table of column in pgadmin1.20.0 To: Akshay Joshi Cc: pgadmin-support , JasmineLiu Content-Type: multipart/alternative; boundary=001a11c3ca1e9827d3052220605c X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgadmin-support Precedence: bulk Sender: pgadmin-support-owner@postgresql.org --001a11c3ca1e9827d3052220605c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Thu, Oct 15, 2015 at 11:15 AM, JasmineLiu wrote: > Hi, all ! > > This is Liu Yuanyuan. > I find the inherited table of column shown in pgadmin 1.20.0, sometimes > isn=E2=80=99t right. That should be a bug. > Hope someone to do something about this problem! > Here is my example: > > First I execute the following sql in pgadmin 1.20.0 by query tool: > create schema test; > create table test.a1(id int); > create table test.a2(id int, name varchar); > create table test.a3(age int); > create table test.aa() inherits(test.a1,test.a2,test.a3); > > > Then in main view of pgadmin 1.20.0=EF=BC=9A > It shows the column age is inherited from table test.a2, this is not righ= t. > > > Looks like a bug to me. Akshay, Can you please take a look at it? -- Thanks & Regards, Ashesh Vashi EnterpriseDB INDIA: Enterprise PostgreSQL Company *http://www.linkedin.com/in/asheshvashi* > > I also check the code of pgadmin 1.20.0, I think the method to specify th= e > inherited table of columns is not correct,especially when the inherited > tables have same column. > > Thanks and hope to hear from you soon! > > Best wishes! > Liu Yuanyuan > > > > > -- > View this message in context: > http://postgresql.nabble.com/Error-about-inherited-table-of-column-in-pga= dmin1-20-0-tp5870044.html > Sent from the PostgreSQL - pgadmin support mailing list archive at > Nabble.com. > > > -- > Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgadmin-support > --001a11c3ca1e9827d3052220605c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Thu,= Oct 15, 2015 at 11:15 AM, JasmineLiu <liuyuanyuangogo@gmail.com> wrote:
Hi, all = !

This is Liu Yuanyuan.
I find the inherited table of column shown in pgadmin 1.20.0, sometimes
isn=E2=80=99t right. That should be a bug.
Hope someone to do something about this problem!
Here is my example:

First I execute the following sql in pgadmin 1.20.0 by query tool:
create schema test;
create table test.a1(id int);
create table test.a2(id int, name varchar);
create table test.a3(age int);
create table test.aa() inherits(test.a1,test.a2,test.a3);


Then in main view of pgadmin 1.20.0=EF=BC=9A
It shows the column age is inherited from table test.a2, this is not right.=
<http://postgresql.nabble.com/file/n5870044/1.jpg= >
<http://postgresql.nabble.com/file/n5870044/2.jpg= >
Looks like a bug to me.

Akshay,<= br>
Can you please take a look at it?

--

Thanks & Regards,

Ashesh Vashi
EnterpriseDB INDIA: Enterprise PostgreSQL Company

<= br>

<= a href=3D"http://www.linkedin.com/in/asheshvashi" target=3D"_blank">http= ://www.linkedin.com/in/asheshvashi

= =C2=A0

I also check the code of pgadmin 1.20.0, I think the method to specify the<= br> inherited table of columns is not correct,especially when the inherited
tables have same column.

Thanks and hope to hear from you soon!

Best wishes!
Liu Yuanyuan




--
View this message in context: http://postgresql.nabble.com/Error-about-inheri= ted-table-of-column-in-pgadmin1-20-0-tp5870044.html
Sent from the PostgreSQL - pgadmin support mailing list archive at Nabble.c= om.


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

--001a11c3ca1e9827d3052220605c--