Re: ECPG: store own copy of the prepared statement name

Поиск
Список
Период
Сортировка
От Boszormenyi Zoltan
Тема Re: ECPG: store own copy of the prepared statement name
Дата
Msg-id 4AD70C35.7010009@cybertec.at
обсуждение исходный текст
Ответ на Re: ECPG: store own copy of the prepared statement name  (Michael Meskes <meskes@postgresql.org>)
Список pgsql-hackers
Michael Meskes írta:
> On Wed, Oct 14, 2009 at 06:37:43PM +0200, Boszormenyi Zoltan wrote:
>   
>> the attached patch makes ECPG more robust
>> against applications that free() strings by storing
>> its own copy of the prepared statement name.
>>     
>
> Please do not call strdup() directly in libecpg. Instead please use
> ecpg_strdup() which does all the error handling needed. I changed this and
> committed the patch. Thanks.
>
> Michael
>   

Thanks, I will keep it in mind.

Best regards,
Zoltán Böszörményi

-- 
Bible has answers for everything. Proof:
"But let your communication be, Yea, yea; Nay, nay: for whatsoever is more
than these cometh of evil." (Matthew 5:37) - basics of digital technology.
"May your kingdom come" - superficial description of plate tectonics

----------------------------------
Zoltán Böszörményi
Cybertec Schönig & Schönig GmbH
http://www.postgresql.at/



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Michael Meskes
Дата:
Сообщение: Re: ECPG: store own copy of the prepared statement name
Следующее
От: "mingsoftt"
Дата:
Сообщение: visual c++ compile error when included spi.h and trigger.h