-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alexander Borkowski
Sent: 11 October 2004 08:31
To: [EMAIL PROTECTED]
Subject: [pgadmin-hackers] Foreign keys / MATCH FULL, PARTIAL, etc.
I don't know of how much help this is going to be, but the anwer to the question
// MATCH FULL/PARTIAL missing; where is this stored?!?
posed in pgForeignKey.cpp line 45 is: In pg_catalog.pg_trigger.tgargs. It is the third argument (zero based) to the ri-triggers, or more precisely the RI_MATCH_TYPE_ARGNO'th, cf. include/commands/trigger.h in the PostgreSQL 8.0 beta 3 source (7.4 as well).
Ahh, thanks Alex. Iirc, that comment was written in 7.3 days when the dcos said something like "There's MATCH FULL and MATCH PARTIAL which isn't implemented yet", so it was probably ignored. Of course, there was also MATCH SIMPLE, but it didn't have a name then, and cursory scan of the docs probably wouldn't have registered it's existance :-(
AFAIR at the moment of implementing that part the 7.3 doc didn't fully document pg_constraint. The correct answer to this question now is pg_constraint.confmatchtype.
We'll fix this for 1.3/1.4. It requires dialog changes, so this has to wait a little. Thanks for pointing out this missing option, we'd probably would have missed it up to pgsql 2030 :-)
Regards, Andreas
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
