Re: [HACKERS] regproc fix

Bruce Momjian wrote:
>
> > > > > 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
> > > > automatically.
> But no one really assigns regproc fields.  They usually do it through
> CREATE FUNCTION, and that would still require the quotes, so is it
> worth making that exception?

If you don't think so, no! ;-)

                       - Tom