> > One remaining problem is that you have to supply the oid in quotes,
> > because regproc has to get a string, not an int. Perhaps we need
> > another regprocin that allows int4 or char*, but I don't think you can
> > allow two input functions for a type.
> > Perhaps we can just leave it. We also output the proname, even if
> > they used the oid as input.
> The int4 vs. string issue would be easily solved by having a routine
> regproc(int4), which the new type coersion stuff would use
But we define a pg_type.typinput. What do we put in there. I assume we
can leave it alone, and allow the type coersion stuff to over-ride it.
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
In response to
pgsql-hackers by date
|Next:||From: Bruce Momjian||Date: 1998-10-02 14:47:16|
|Subject: Re: [HACKERS] Open 6.4 items|
|Previous:||From: Bruce Momjian||Date: 1998-10-02 14:43:36|
|Subject: Re: [HACKERS] Names that suddenly include an OID|