| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: User defined I/O conversion casts |
| Date: | 2008-10-30 13:37:37 |
| Message-ID: | 11671.1225373857@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> writes:
> Yeah, a magical OID clearly has some issues. A new field in pg_cast is
> the obvious alternative. How about adding a "castmethod" char field,
> with values:
> b = binary-compatible cast (CREATE CAST ... WITHOUT FUNCTION)
> i = I/O coercion cast (the new beast, CREATE CAST ... WITH INOUT)
> f = use cast function specified in castfunc field.
> castfunc is 0 for methods b and i.
Seems sane to me. If you do that, please add a check in the opr_sanity
regression test that castfunc is nonzero if and only if castmethod is f.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2008-10-30 13:46:18 | Re: User defined I/O conversion casts |
| Previous Message | Heikki Linnakangas | 2008-10-30 13:31:14 | Re: User defined I/O conversion casts |