Re: Use lo_creat() when possible instead of lo_create() - Mailing list psycopg

From Daniele Varrazzo
Subject Re: Use lo_creat() when possible instead of lo_create()
Date
Msg-id CA+mi_8am5aixtKDTttML4Pmeds=CMfbqGOC_1+k6jCzZPKoNDQ@mail.gmail.com
Whole thread Raw
In response to Re: Use lo_creat() when possible instead of lo_create()  (Daniele Varrazzo <daniele.varrazzo@gmail.com>)
List psycopg
On Tue, Jan 10, 2012 at 12:18 PM, Daniele Varrazzo
<daniele.varrazzo@gmail.com> wrote:
> On Tue, Jan 10, 2012 at 10:06 AM, Federico Di Gregorio <fog@dndg.it> wrote:
>> On 10/01/12 09:51, Giovanni Mascellani wrote:
>>>
>>> I just created a ticket against psycopg2, and Daniele asked me to bring
>>> the issue on the list to open it to a wider audience. The ticket is here:
>>>
>>>
>>> http://psycopg.lighthouseapp.com/projects/62710/tickets/88-use-lo_creat-when-possible-instead-of-lo_create
>>
>>
>> The patch seems fine to me. Doesn't add any overhead and improves
>> compatibility with an existing product. I vote +1 [that means "unless
>> Daniele votes -1 I'll include it" ;)]
>
> I don't know much about the difference between the two functions: if
> anybody has any interesting story about them I'd be happy to know.
> Meanwhile I'll make sure we have tests for both the code paths in the
> patch.

I've made some tests and everything seems fine. I've integrated the
patch in my branch.

-- Daniele

psycopg by date:

Previous
From: Daniele Varrazzo
Date:
Subject: Re: Use lo_creat() when possible instead of lo_create()
Next
From: maplabs@light42.com
Date:
Subject: large return resuls