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

Re: Bugs: Programming Language Functions

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Andrew C(dot)R(dot) Martin" <a(dot)c(dot)r(dot)martin(at)reading(dot)ac(dot)uk>
Cc: interfaces(at)postgresql(dot)org, docs(at)postgresql(dot)org, hackers(at)postgresql(dot)org
Subject: Re: Bugs: Programming Language Functions
Date: 2000-04-11 16:05:39
Message-ID: 1291.955469139@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-docspgsql-interfaces
"Andrew C.R. Martin" <a(dot)c(dot)r(dot)martin(at)reading(dot)ac(dot)uk> writes:
> My own particular problem simply pulls out an integer and a (text *)
> from a varchar. It then goes away and does some calculations based on
> these values and another external file (in fact it does a system() to
> run an external program which does these calculations). It then build
> a 'text' structure containing the result.

Hm.  I'm not too clear on why that would need to worry about either
TupleTableSlot or GetAttributeByName ... shouldn't it be a simple
function consuming a text Datum and producing another?

			regards, tom lane

In response to

Responses

pgsql-docs by date

Next:From: Andrew C.R. MartinDate: 2000-04-11 17:04:17
Subject: Re: [HACKERS] Re: Bugs: Programming Language Functions
Previous:From: jonDate: 2000-04-11 15:46:31
Subject: Re: Re: Postgres vs. PostgreSQL

pgsql-interfaces by date

Next:From: Andrew C.R. MartinDate: 2000-04-11 17:04:17
Subject: Re: [HACKERS] Re: Bugs: Programming Language Functions
Previous:From: Andrew C.R. MartinDate: 2000-04-11 15:38:58
Subject: Re: Bugs: Programming Language Functions

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