From: Michael Meskes <Michael_Meskes@topmail.de>
To: PostgreSQL Interfaces <pgsql-interfaces@postgresql.org>
Subject: ecpg idea
Date: Sat, 20 Feb 1999 19:07:34 +0100
Message-ID: <19990220190734.A896@gmx.net> (raw)
James just asked me about a new feature in ecpg that I certainly not heard
about yet. However, I think it is a good idea.
Let's say we have the following statement:
exec sql select name into :stringvar from address;
Then stringvar has to be a variable with enough room to store the string. In
contrast to Oracle we allow stringvar to be either an array of char or a
pointer (and the varchar alternatives). However, if you provide a char * you
have to make sure it has memory allocated yourself. James now asked me to to
the correct malloc() inside libecpg if that poointer is NULL.
I never heard about a feature like this on other DBMS but I like the idea.
It should be pretty easy to implement too. Unless it is strictly against
standard I would like to implement it.
Comments anyone?
Michael
--
Michael Meskes | Go SF 49ers!
Th.-Heuss-Str. 61, D-41812 Erkelenz | Go Rhein Fire!
Tel.: (+49) 2431/72651 | Use Debian GNU/Linux!
Email: Michael.Meskes@gmx.net | Use PostgreSQL!
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: Michael_Meskes@topmail.de
Subject: Re: ecpg idea
In-Reply-To: <19990220190734.A896@gmx.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox