Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] regproc fix

From: "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu>
To: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
Cc: hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] regproc fix
Date: 1998-10-02 16:23:10
Message-ID: 3614FDEE.50A0C17B@alumni.caltech.edu (view raw or flat)
Thread:
Lists: pgsql-hackers
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

In response to

pgsql-hackers by date

Next:From: Bruce MomjianDate: 1998-10-02 16:23:23
Subject: Re: [HACKERS] patching utilities?
Previous:From: Bruce MomjianDate: 1998-10-02 16:21:36
Subject: Re: [HACKERS] Patch - please apply

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group