From: | Andrew Chernow <ac(at)esilo(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | Merlin Moncure <mmoncure(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: libpq object hooks (libpq events) |
Date: | 2008-09-03 17:14:03 |
Message-ID: | 48BEC5DB.7000601@esilo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Alvaro Herrera wrote:
> Andrew Chernow escribió:
>> Alvaro Herrera wrote:
>
>>> (I also removed PQresultAlloc.)
>> Nooooooo ... removing PQresultAlloc breaks libpqtypes! It also removes
>> some of the use cases provided by PQsetvalue, which allows one to add to
>> a result (in our case from scratch).
>
> I don't really see the point -- it's the same as pqResultAlloc, except
> that you have to pass an extra argument. There's no actual
> functionality loss.
>
libpqtypes uses it. libpqtypes doesn't have access to any internals of
libpq, including pqResultAlloc. So, I made a public wrapper to the
internal version. The point is to provide public access to the result
allocator.
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Hannu Krosing | 2008-09-03 17:18:02 | Re: [PATCH] Cleanup of GUC units code |
Previous Message | Tom Lane | 2008-09-03 17:13:33 | Re: Function call order dependency |
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Chernow | 2008-09-03 22:10:53 | Re: libpq events patch |
Previous Message | Alvaro Herrera | 2008-09-03 17:02:49 | Re: libpq events patch |