Re: Re: [HACKERS] New parameter RollbackError to control rollback behavior on error
| От | Hiroshi Inoue | 
|---|---|
| Тема | Re: Re: [HACKERS] New parameter RollbackError to control rollback behavior on error | 
| Дата | |
| Msg-id | 5335F4C3.7050004@tpf.co.jp обсуждение исходный текст  | 
		
| Ответ на | Re: Re: [HACKERS] New parameter RollbackError to control rollback behavior on error (Michael Paquier <michael.paquier@gmail.com>) | 
| Ответы | 
                	
            		Re: Re: [HACKERS] New parameter RollbackError to control
 rollback behavior on error
            		
            		 Re: Re: [HACKERS] New parameter RollbackError to control rollback behavior on error  | 
		
| Список | pgsql-odbc | 
(2014/03/28 14:37), Michael Paquier wrote:
> On Fri, Mar 28, 2014 at 12:53 PM, Inoue, Hiroshi <inoue@tpf.co.jp> wrote:
>> (2014/03/27 20:55), Michael Paquier wrote:
>>>
>>> (Moving back this thread to pgsql-odbc, so keeping a maximum of message
>>> history)
>>
>>
>> As for the patch in the original post,
>>
>> Is there any difference between rollback_on_error and
>> rollback_error_value except the naming?
> No differences. I just changed the name of this variable to be a
> maximum consistent with the parameter introduced.
There are some rollback_on_error in dlg_wingui.c.
>> The length of connection strings seem to be increased at least 3 bytes.
>> Is it right?
> Do you mean that with the introduction of the new parameter AA? If
> yes, well I guess it is increased by 5 bytes ";AA=[0|1|2]".
Isn't the difference between
    A1=7.4;AA=[0|1|2]  and  A1=7.4-[0|1|2]
?
I introduced the latter only to skimp on 3 bytes.
regards,
Hiroshi Inoue
		
	В списке pgsql-odbc по дате отправления: