| From: | Tom Dunstan <pgsql(at)tomd(dot)cc> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Matt Miller <pgsql(at)mattmillersf(dot)fastmail(dot)fm>, Neil Conway <neilc(at)samurai(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: "anyelement2" pseudotype |
| Date: | 2007-02-19 14:51:07 |
| Message-ID: | 45D9B95B.1030801@tomd.cc |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> I realized that I can probably fix ATAddForeignKeyConstraint to do the
> right thing by having it pass the two actual column types to
> can_coerce_type, thus allowing check_generic_type_consistency to kick
> in and detect the problem.
Yeah, I came to the same conclusion. No amount of refactoring in
parse_coerce.c is going to get the original concrete types back to
compare. That should fix the problem with arrays, enums and any
potential future generic types without mentioning them explicitly in
there a la the hack there currently, thankfully.
Cheers
Tom
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-02-19 14:57:32 | Re: Chatter on DROP SOMETHING IF EXISTS |
| Previous Message | Guillaume Smet | 2007-02-19 14:39:02 | Re: WIP patch - INSERT-able log statements |