> On Wed, Nov 14, 2018 at 6:01 PM Dmitry Dolgov <9erthali...@gmail.com> wrote:
>
> > On Wed, 13 Jun 2018 at 06:30, Kato, Sho wrote:
> >
> > I add a function called ECPGfreeSQLDA() becasue there is no API for
> > releasing the SQLDA stored the result set.
> >
> > On Mon, 18 Jun 2018 at 07:42,
> On Wed, 13 Jun 2018 at 06:30, Kato, Sho wrote:
>
> I add a function called ECPGfreeSQLDA() becasue there is no API for releasing
> the SQLDA stored the result set.
>
> On Mon, 18 Jun 2018 at 07:42, Thomas Munro
> wrote:
>
> I wonder how other ESQL/C implementations deal with this stuff (...)
On Tue, Jun 19, 2018 at 9:11 PM, Kato, Sho wrote:
>>This is not clear to me. ECPGfreeSQLDA() releases a whole chain, but
>>free() only releases a single SQLDA(), so they are obviously not
>>interchangeable. When exactly should a user prefer one over the other?
>
> If an application use FETCH
On Wed, Jun 13, 2018 at 4:29 PM, Kato, Sho wrote:
> I add a function called ECPGfreeSQLDA() becasue there is no API for releasing
> the SQLDA stored the result set.
Hello Kato-san,
Thank you for sending the patch!
+ Alternatively, use the standard C library's free() function as
in the
Hi,
I add a function called ECPGfreeSQLDA() becasue there is no API for releasing
the SQLDA stored the result set.
An example of usage is as follows.
Specify a pointer to sqlda_t to be released as an argument.
Example:
exec sql begin declare section;
char*stmt1 = "SELECT *
