Search Postgresql Archives

Re: Libpq question

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Jasen Betts <jasen@xxxxxxxxxx> writes:
> On 2012-05-16, John Townsend <jtownsend@xxxxxxxxxxxxxxxxxxxx> wrote:
>> *** So...the question: Is there a good reason why you might want to NOT 
>> use libpq.dll, and just directly access the server through direct 
>> function calls? ***

> libpq binds you to using NUL terminated C strings, and, no doubt, other C
> idioms.

Note that bypassing libpq will not get you around that one, because the
server (and indeed the wire protocol) also use nul-terminated strings.

Generally the places where people have chosen to reimplement the
protocol from scratch are where they *couldn't* use libpq for some
reason or other; for instance the JDBC driver doesn't use libpq because
non-Java code is painful to deal with in a Java environment.  I'm pretty
doubtful that it's worth anybody's trouble to reimplement just to save a
layer of function calls.

			regards, tom lane

-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux