Re: [pgadmin-hackers] PATCH: To fix the issue in exclusion constraint (pgAdmin4) - Mailing list pgadmin-hackers

From Dave Page
Subject Re: [pgadmin-hackers] PATCH: To fix the issue in exclusion constraint (pgAdmin4)
Date
Msg-id CA+OCxoxRTEN2L=mF2m0zgKQYVdpFSQ=-ixO0j-3dwKA=SNvO9Q@mail.gmail.com
Whole thread Raw
In response to [pgadmin-hackers] PATCH: To fix the issue in exclusion constraint (pgAdmin4)  (Murtuza Zabuawala <murtuza.zabuawala@enterprisedb.com>)
Responses Re: [pgadmin-hackers] PATCH: To fix the issue in exclusion constraint (pgAdmin4)  (Dave Page <dpage@pgadmin.org>)
List pgadmin-hackers
Hi

On Mon, Jan 9, 2017 at 10:46 AM, Murtuza Zabuawala
<murtuza.zabuawala@enterprisedb.com> wrote:
> Hi Dave,
>
> I followed,
>
> 1) First click on main properties panel.
>
> 2) Sample definition,
>
> CREATE TABLE public.test_table
> (
>     id character varying(3) COLLATE pg_catalog."default" NOT NULL,
>     col1 bigint,
>     CONSTRAINT test_pkey PRIMARY KEY (id)
> )
> WITH (
>     OIDS = FALSE
> )
> TABLESPACE pg_default;
>
> With above created table, create exclusion constraint with following options
> using GUI,
>
> ALTER TABLE public.test_table
>     ADD CONSTRAINT test_exclu EXCLUDE USING btree (
>     col1 DESC NULLS LAST WITH =);
>
> Click on Save, Exclusion constraint will be created successfully but you
> will get error as wrong OID was sent while generating node info.

Nope - it works fine for me. I wonder what's different...



--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgadmin-hackers by date:

Previous
From: Harshal Dhumal
Date:
Subject: Fwd: [pgadmin-hackers] Patch for RM1911 Direct file navigation[pgAdmin4] [Feature]
Next
From: Dave Page
Date:
Subject: [pgadmin-hackers] pgAdmin 4 commit: Use the correct OID for retrieving properties offres