From: | Murtuza Zabuawala <murtuza(dot)zabuawala(at)enterprisedb(dot)com> |
---|---|
To: | "microsys(dot)gr microsys(dot)gr" <microsys(dot)gr(at)gmail(dot)com> |
Cc: | pgAdmin Support <pgadmin-support(at)postgresql(dot)org> |
Subject: | Re: PRIMARY KEY FIELDS DISPLAY ORDER |
Date: | 2017-01-16 04:51:08 |
Message-ID: | CAKKotZRoT_xG1FN9cbKxQqX4Q4LFfkMmg_ovLALUMohf8pMAuQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
Hi,
This issue has been fixed RM#1842 & fix will be available in next release.
--
Regards,
Murtuza Zabuawala
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
On Sun, Jan 15, 2017 at 9:25 PM, microsys.gr microsys.gr <
microsys(dot)gr(at)gmail(dot)com> wrote:
> OS Windows 10
> pgAdmin 4 Version1.1
> Python Version 2.7.11
> Flask Version 0.11.1
> Application Mode Desktop
> ---------------------------------
>
> When browse tables,
>
> 1)
> in SQL panel
> ...
> CONSTRAINT mytable_pkey PRIMARY KEY (field1, field2, field3,...)
> ...
> the order the fields are displayed is NOT correct.
>
> 2)
> same wrong order in Constraint subtree SQL panel,
>
> ALTER TABLE public.mytable
> ADD CONSTRAINT mytable_pkey PRIMARY KEY (field1, field2, field3,...);
>
> 3)
> same wrong order in table popup menu -> Properties -> [window form]->
> Constraints tab
>
> ------------------------------------------------------------------
> 4)
> But in Properties panel, fields are displayed correctly.
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Shira Bezalel | 2017-01-17 18:13:11 | Function not displaying PARALLEL SAFE on SQL tab |
Previous Message | microsys.gr microsys.gr | 2017-01-15 16:38:10 | TABLE IMPORT/EXPORT NOT WORKING |