From: | Greg Stark <gsstark(at)mit(dot)edu> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Greg Stark <gsstark(at)mit(dot)edu>, Stephen Frost <sfrost(at)snowman(dot)net>, Martijn van Oosterhout <kleptog(at)svana(dot)org>, Dave Page <dpage(at)vale-housing(dot)co(dot)uk>, pgsql-hackers(at)postgresql(dot)org, Hiroshi Inoue <inoue(at)tpf(dot)co(dot)jp> |
Subject: | Re: Practical impediment to supporting multiple SSL libraries |
Date: | 2006-04-13 20:26:28 |
Message-ID: | 87odz5gr2j.fsf@stark.xeocode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> Greg Stark <gsstark(at)mit(dot)edu> writes:
> > I think there's some confusion about what problem this is aiming to solve. I
> > thought the primary problem ODBC and other drivers have is just that they want
> > to be able to fetch whatever records are available instead of waiting for the
> > entire query results to be ready.
>
> No, that's not what I'm thinking about at all, and I don't think Martijn
> is either. The point here is that ODBC wants to store the resultset in
> a considerably different format from what libpq natively provides, and
> we'd like to avoid the conversion overhead.
So how would you provide the data to the callback? And how does having a
callback instead of a regular downcall give you any more flexibility in how
you present the data?
--
greg
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2006-04-13 20:41:33 | Re: Practical impediment to supporting multiple SSL libraries |
Previous Message | Stephen Frost | 2006-04-13 19:42:44 | Re: Practical impediment to supporting multiple SSL libraries |