Re: [HACKERS] Embedded SQL question

From: Michael Meskes <Michael_Meskes(at)topmail(dot)de>
To: PostgreSQL Hacker <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: [HACKERS] Embedded SQL question
Date: 1999-02-09 19:09:03
Message-ID: 19990209200903.A928@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Feb 09, 1999 at 10:14:26AM +0100, Zeugswetter Andreas IZ5 wrote:
>
> free is the opposite to prepare, a statement stays prepared until free is
> called.
> This will release all associated resources. In my Informix manual it sais,
> that
> it will not affect an already declared cursor on this statement.
>
> exec sql prepare d_id from :stmt;
> ....
> exec sql free d_id;

Oh, that's easy. :-) I already have it with the standard syntax 'exec sql
deallocate prepare'.

> > exec sql alloc
>
> All I find for this is:
> exec sql allocate descriptor :descname [with max :colmax];
> allocates memory for a system descriptor area (sqlca) for a maximum of
> colmax columns (default 100) for use with a describe statement.

Guess this has to wait some more.

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(dot)Meskes(at)gmx(dot)net | Use PostgreSQL!

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter T Mount 1999-02-09 21:07:49 Re: [HACKERS] Problems with >2GB tables on Linux 2.0
Previous Message Jan Wieck 1999-02-09 18:38:10 Re: AW: [HACKERS] Problems with >2GB tables on Linux 2.0