Re: Time for a release?

On 29/07/11 09:20, ZIGLIO, Frediano, VF-IT wrote:
>> On 29/07/2011 07:35, ZIGLIO, Frediano, VF-IT wrote:
>>>> Hi,
>>>>
>>>> I think it may be worth turning 2.3.1pre into a 2.3.1 release.
>>>>
>>>> Does anyone have any outstanding issues with 2.3.1pre that
>> they would
>>>> like resolving before I do the release?
>>>>
>>> Did you fix the SQLCancel thread problem?
>>> SQLCancel can be called from another thread to cancel for
>> instance a
>>> SQLExecDirect on the same statement with any threading
>> model just stop
>>> due to lock waiting SQLExecDirect to finish instead of
>> cancelling it.
>>> Regards,
>>>     Frediano
>> Well, the default is to assume the driver is thread safe so
>> there is no restriction on when the driver is called.
>>
>> if thats the problem you refer to.
>>
>> If the driver isnt thread safe, then this will still fail,
>> but if the driver isn't thread safe what can I do?
>>
> Just downloaded last stable version (2.3.0) and checked.
> The default threading level is 3 that is lock the entire environment
> (see thread_protect).

Ok, thats my mistake, I must have changed the default and not commited.

So, bit late for this change, but see if the one there now works for 
most folks. The entry in Changes:

     * Change default threading protection to 0, most drivers should be 
thread
       safe by now. If the driver is at all thread safe, allow SQLCancel 
to bipass the
       interlock.

-- 
Nick
_______________________________________________
unixODBC-dev mailing list
[email protected]
http://mailman.unixodbc.org/mailman/listinfo/unixodbc-dev