| From: | James Thompson <jamest(at)math(dot)ksu(dot)edu> |
|---|---|
| To: | Michael Meskes <Michael_Meskes(at)topmail(dot)de> |
| Cc: | PostgreSQL Interfaces <pgsql-interfaces(at)postgreSQL(dot)org> |
| Subject: | Re: [INTERFACES] ecpg idea |
| Date: | 1999-02-20 18:45:27 |
| Message-ID: | Pine.GSO.4.05.9902201238220.5372-100000@noether.math.ksu.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-interfaces |
On Sat, 20 Feb 1999, Michael Meskes wrote:
>
> 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?
You know you have my vote! :-)
I'll retract my previous private statement about compatibility with Oracle
being important. After thinking about it some more I'd much rather have a
superiour free product than compatiblility with a comercial product.
The only issue I can forsee is when virtual memory is exhausted, would
this require additional error code defined that would violate some sql
standard? And would a NULL pointer on return siginfy a null column value
in the table or a failed malloc?
->->->->->->->->->->->->->->->->->->---<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<
James Thompson 138 Cardwell Hall Manhattan, Ks 66506 785-532-0561 Kansas
State University Department of Mathematics
->->->->->->->->->->->->->->->->->->---<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<
| From | Date | Subject | |
|---|---|---|---|
| Next Message | James Thompson | 1999-02-20 18:56:28 | Re: [INTERFACES] ecpg idea |
| Previous Message | Thomas G. Lockhart | 1999-02-20 18:37:47 | Re: [INTERFACES] ecpg idea |