From: | Michael Meskes <Michael_Meskes(at)topmail(dot)de> |
---|---|
To: | PostgreSQL Interfaces <pgsql-interfaces(at)postgresql(dot)org> |
Subject: | ecpg idea |
Date: | 1999-02-20 18:07:34 |
Message-ID: | 19990220190734.A896@gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
James just asked me about a new feature in ecpg that I certainly not heard
about yet. However, I think it is a good idea.
Let's say we have the following statement:
exec sql select name into :stringvar from address;
Then stringvar has to be a variable with enough room to store the string. In
contrast to Oracle we allow stringvar to be either an array of char or a
pointer (and the varchar alternatives). However, if you provide a char * you
have to make sure it has memory allocated yourself. James now asked me to to
the correct malloc() inside libecpg if that poointer is NULL.
I never heard about a feature like this on other DBMS but I like the idea.
It should be pretty easy to implement too. Unless it is strictly against
standard I would like to implement it.
Comments anyone?
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 | Thomas G. Lockhart | 1999-02-20 18:37:47 | Re: [INTERFACES] ecpg idea |
Previous Message | Michael Meskes | 1999-02-20 16:52:58 | Re: [INTERFACES] ecpg: use of #defines |