We just go through code and following are the findings.
Issue :-
To find out the constraint we are using pg_constraint class. In PG 9.2 valid values for "confmatchtype" column in pg_constraint class is (f = full, p = partial, u = simple) But for PG 9.3 valid values are (f = full, p = partial, s = simple).
Because of the above change in PG 9.3 our pgAdmin below logic will fail in pgForeignKey.cpp file and it shows value "MATCH UNKNOWN" in SQL Pane.
On Mon, Aug 19, 2013 at 2:17 PM, Dave Page <dpage@pgadmin.org> wrote:
Dinesh, can you take a look at this please?
Thanks.
On Thu, Aug 15, 2013 at 9:32 AM, Attila Soki <atiware@gmx.net> wrote: > hi, > > when used with postgresql 9.3, pgadmin shows in table definition > ... > CONSTRAINT xy_fkey FOREIGN KEY (xy_id) > REFERENCES tablename (xy_id) MATCH Unknown > > insead of > MATCH SIMPLE > > > before 9.3 for MATCH SIMPLE was confmatchtype=u > since postgresql 9.3 is confmatchtype=s > > cheers, > Attila Soki > > > > -- > Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgadmin-support