Re: deallocating prepared statements

From: "Haszlakiewicz, Eric" <EHASZLA(at)transunion(dot)com>
To: "Michael Meskes" <meskes(at)postgresql(dot)org>
Cc: <pgsql-interfaces(at)postgresql(dot)org>
Subject: Re: deallocating prepared statements
Date: 2008-12-03 17:38:27
Message-ID: 9D29FD18CBD74A478CBA86E6EF6DBAD40308029E@CHI4EVS04.corp.transunion.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-interfaces

>From: Michael Meskes [mailto:meskes(at)postgresql(dot)org]
>On Tue, Dec 02, 2008 at 01:22:46PM -0600, Haszlakiewicz, Eric wrote:
>> figure out how to deallocate prepared statements. I tried
>using esql to
>> do it (since the docs say that "it is only for use in embedded sql"):
>>
>> exec sql begin declare section;
>> const char *stmtName = "exec_stmt";
>> exec sql end declare section;
>> exec sql deallocate :stmtName;
>
>This will not work unless you do more in ECPG. Without
>preparing a statement,
>having a connection etc. there is no way to deallocate the statement.
>
>If you mix libpq and ecpg you should know what you do.

So why is preparing a statement in ecpg different from preparing one
with libpq? Isn't the actual prepare done on the server?

eric

In response to

Responses

Browse pgsql-interfaces by date

  From Date Subject
Next Message Haszlakiewicz, Eric 2008-12-03 17:45:53 Re: deallocating prepared statements
Previous Message Michael Meskes 2008-12-03 14:12:55 Re: deallocating prepared statements