Re: Behavior change of FK info query
- From: "Hiroshi Saito" <z-saito(at)guitar(dot)ocn(dot)ne(dot)jp>
- To: <khanzahid235(at)yahoo(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Craig Ringer" <craig(at)postnewspapers(dot)com(dot)au>, "Dave Page" <dpage(at)pgadmin(dot)org>, <inoue(at)tpf(dot)co(dot)jp>
- Cc: <pgsql-bugs(at)postgresql(dot)org>, <pgsql-odbc(at)postgresql(dot)org>
- Subject: Re: Behavior change of FK info query
- Date: Wed, 5 Nov 2008 00:35:44 +0900
- Message-id: <A3C98AC90C684ECBB819C5A79B80D5FF@HIRO57887DE653> <text/plain>
Hi.
Zahid Khan <khanzahid235(at)yahoo(dot)com> writes:
In my application we are getting different results in 8.2\xA0 and 8.3 servers. if we execute the
query no 3 below after creating table even on psql.As psqlODBC drives executes query no 3 below
to get foreign key information.if we want to reproduce this , we can executes the following
queries on psql in sequence we are getting different results in 8.2\xA0 and 8.3 .
8.3 does not store any foreign-key information in pg_trigger.tgargs
anymore. If psqlODBC is depending on this query then that's a psqlODBC
bug. It'd be better to look at pg_constraint.
Ahh, About foreign key, it will solve by 08.03.0300.
http://psqlodbc.projects.postgresql.org/release.html
I think that it is solvable by 4.).
It seems that I did what point of that mistake.
We has forgotten the information of a release.....sorry.
and, It seems that the test of UUID was not enough.
http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/psqlodbc/psqlodbc/convert.c.diff?r1=1.173&r2=1.174
One more condition fell out.
http://archives.postgresql.org/pgsql-odbc/2008-10/msg00010.php
Furthermore, I think it good to use libpq by which 8.3.5 was released.
So, it is better to pack up 08.03.0310.?
to Dave and Inoue-san.
What do you think?
Regards,
Hiroshi Saito
Home |
Main Index |
Thread Index