Re: Practical impediment to supporting multiple SSL libraries
От | Greg Stark |
---|---|
Тема | Re: Practical impediment to supporting multiple SSL libraries |
Дата | |
Msg-id | 87odz5gr2j.fsf@stark.xeocode.com обсуждение исходный текст |
Ответ на | Re: Practical impediment to supporting multiple SSL libraries (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Practical impediment to supporting multiple SSL libraries
Re: Practical impediment to supporting multiple SSL libraries |
Список | pgsql-hackers |
Tom Lane <tgl@sss.pgh.pa.us> writes: > Greg Stark <gsstark@mit.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
В списке pgsql-hackers по дате отправления: