| From: | Michael Meskes <Michael_Meskes(at)topmail(dot)de> |
|---|---|
| To: | PostgreSQL Interfaces <pgsql-interfaces(at)postgreSQL(dot)org> |
| Subject: | Re: [INTERFACES] ecpg idea |
| Date: | 1999-02-21 11:53:20 |
| Message-ID: | 19990221125320.A346@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-interfaces |
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(dot)Meskes(at)gmx(dot)net | Use PostgreSQL!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Meskes | 1999-02-21 11:54:37 | Re: [INTERFACES] ecpg idea |
| Previous Message | Michael Davis | 1999-02-20 21:24:18 | RE: [INTERFACES] Yet Another ODBC problem... |