From: Michael Meskes <Michael_Meskes@topmail.de>
To: PostgreSQL Interfaces <pgsql-interfaces@postgreSQL.org>
Subject: Re: [INTERFACES] ecpg idea
Date: Sun, 21 Feb 1999 12:53:20 +0100
Message-ID: <19990221125320.A346@gmx.net> (raw)
In-Reply-To: <Pine.GSO.4.05.9902201238220.5372-100000@noether.math.ksu.edu>
References: <19990220190734.A896@gmx.net>
<Pine.GSO.4.05.9902201238220.5372-100000@noether.math.ksu.edu>
On Sat, Feb 20, 1999 at 12:45:27PM -0600, James Thompson wrote:
> The only issue I can forsee is when virtual memory is exhausted, would
> this require additional error code defined that would violate some sql
I don't see that. There is already an OUT_OF_MEMORY error message.
> standard? And would a NULL pointer on return siginfy a null column value
> in the table or a failed malloc?
A failed malloc. Null values are only transfered via indicators.
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.Meskes@gmx.net | Use PostgreSQL!
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: Michael_Meskes@topmail.de
Subject: Re: [INTERFACES] ecpg idea
In-Reply-To: <19990221125320.A346@gmx.net>
* 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