From: Thomas G. Lockhart <lockhart@alumni.caltech.edu>
To: Michael Meskes <Michael_Meskes@topmail.de>
Cc: PostgreSQL Interfaces <pgsql-interfaces@postgreSQL.org>
Subject: Re: [INTERFACES] ecpg idea
Date: Sat, 20 Feb 1999 18:37:47 +0000
Message-ID: <36CF00FB.53393C31@alumni.caltech.edu> (raw)
References: <19990220190734.A896@gmx.net>
> ... 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
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: lockhart@alumni.caltech.edu, Michael_Meskes@topmail.de
Subject: Re: [INTERFACES] ecpg idea
In-Reply-To: <36CF00FB.53393C31@alumni.caltech.edu>
* 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