From: | "John Huttley" <john(at)mwk(dot)co(dot)nz> |
---|---|
To: | <pgsql-interfaces(at)postgreSQL(dot)org> |
Subject: | Re: [INTERFACES] C tuples (For V7 please, hackers!) |
Date: | 1999-06-24 01:09:04 |
Message-ID: | 00e401bebdde$27dc7020$1401a8c0@Mr_Creosote.MWK.co.nz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
I've been recently moving apps between databases and have found that the
major
limitation with postgresql is the inability of stored procedures to return a
record set.
The aim should be to be able to transparently replace a table with a stored
procedure.
This might mean supplementing the existing function mechanism with something
new.
IMHO, this is _more_important_ than removing the 8K tuple limit.
Regards,
-----Original Message-----
From: Collin F. Lynch <clynch(at)water2(dot)cs(dot)umass(dot)edu>
To: pgsql-interfaces(at)postgreSQL(dot)org <pgsql-interfaces(at)postgreSQL(dot)org>
Date: Thursday, 24 June 1999 02:54
Subject: [INTERFACES] C tuples
> Greetings, I'm attempting to write some custom C code to access tuples
from within
>the database, more particularly to return tuples. Externally I know that I
can make use of the
>psql sql access but what about internally? The programmer's refrence
assures me that such a
>thing is possible but refuses to elaborate.
> Does anyone know how or where to obtain such elaboration.
>
> Collin Lynch.
>
From | Date | Subject | |
---|---|---|---|
Next Message | Vadim Mikheev | 1999-06-24 01:21:15 | Re: [INTERFACES] Performance |
Previous Message | Kristofer Munn | 1999-06-23 23:31:10 | Perl 5 Interface on 6.5 and lo_creat/lo_open problem |