Received: from golem.jpl.nasa.gov (IDENT:root@hectic-3.jpl.nasa.gov
	[128.149.68.205]) by hub.org (8.9.2/8.9.1) with ESMTP id NAA37556
	for <pgsql-interfaces@postgreSQL.org>;
	Sat, 20 Feb 1999 13:38:28 -0500 (EST)
	(envelope-from lockhart@alumni.caltech.edu)
Received: from alumni.caltech.edu (localhost [127.0.0.1])
	by golem.jpl.nasa.gov (8.8.5/8.8.5) with ESMTP id SAA13294;
	Sat, 20 Feb 1999 18:37:47 GMT
Sender: tgl@mythos.jpl.nasa.gov
Message-ID: <36CF00FB.53393C31@alumni.caltech.edu>
Date: Sat, 20 Feb 1999 18:37:47 +0000
From: "Thomas G. Lockhart" <lockhart@alumni.caltech.edu>
Organization: Caltech/JPL
X-Mailer: Mozilla 4.07 [en] (X11; I; Linux 2.0.36 i686)
MIME-Version: 1.0
To: Michael Meskes <Michael_Meskes@topmail.de>
CC: PostgreSQL Interfaces <pgsql-interfaces@postgreSQL.org>
Subject: Re: [INTERFACES] ecpg idea
References: <19990220190734.A896@gmx.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

> ... if you provide a char * you have to make sure it has memory 
> allocated yourself. James now asked me to do 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?

How do you get back the handle for the newly malloc'd storage?

                     - Tom