| From: | Alexander Borkowski <alexander(dot)borkowski(at)abri(dot)une(dot)edu(dot)au> |
|---|---|
| To: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de>, Dave Page <dpage(at)vale-housing(dot)co(dot)uk> |
| Cc: | pgadmin-hackers(at)postgresql(dot)org |
| Subject: | Re: Foreign keys / MATCH FULL, PARTIAL, etc. |
| Date: | 2004-10-12 07:48:26 |
| Message-ID: | 416B8C4A.3010304@abri.une.edu.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
Andreas Pflug wrote:
>>> // MATCH FULL/PARTIAL missing; where is this stored?!?
> 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.
Yep, that is a lot better and easier to access too. My enthusiasm got me
carried away after I found my "answer", so I didn't do any further
investigation. Sorry.
> We'll fix this for 1.3/1.4.
Thanks for that!
> Thanks for pointing out this missing option, we'd
> probably would have missed it up to pgsql 2030 :-)
I just happend to need it and wondered why it wasn't there. And it is
very reassuring to know that there are no plans to abandon this
excellent software in the near future :-)
Regards,
Alex
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Borkowski | 2004-10-12 08:01:16 | Bug in function property dialog |
| Previous Message | cvs | 2004-10-11 14:23:25 | CVS Commit by dpage: Backout dialogue maximised/iconised size/pos saving |