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? -- -- Nick _______________________________________________ unixODBC-dev mailing list unixODBC-dev <at> mailman.unixodbc.org http://mailman.unixodbc.org/mailman/listinfo/unixodbc-dev
Hi, Nick, On Thu, Jul 28, 2011 at 2:55 AM, Nick Gorham <nick <at> lurcher.org> 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? Is GUI part ready? Thank you. > > -- > Nick > _______________________________________________ > unixODBC-dev mailing list > unixODBC-dev <at> mailman.unixodbc.org > http://mailman.unixodbc.org/mailman/listinfo/unixodbc-dev > _______________________________________________ unixODBC-dev mailing list unixODBC-dev <at> mailman.unixodbc.org http://mailman.unixodbc.org/mailman/listinfo/unixodbc-dev
On 28/07/2011 19:01, Igor Korot wrote: > Hi, Nick, > > On Thu, Jul 28, 2011 at 2:55 AM, Nick Gorham<nick <at> lurcher.org> 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? > Is GUI part ready? > > Thank you. I don't know. The two parts are not connected now. Peter? -- -- Nick _______________________________________________ unixODBC-dev mailing list unixODBC-dev <at> mailman.unixodbc.org http://mailman.unixodbc.org/mailman/listinfo/unixodbc-dev
Could be... have been working on other projects but could turn my attention to the GUI bits if there is a need (ie someone from one or more of the distro teams needs). -- Peter Nick Gorham wrote: > On 28/07/2011 19:01, Igor Korot wrote: >> Hi, Nick, >> >> On Thu, Jul 28, 2011 at 2:55 AM, Nick Gorham<nick <at> lurcher.org> 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? >> Is GUI part ready? >> >> Thank you. > > I don't know. The two parts are not connected now. Peter? > _______________________________________________ unixODBC-dev mailing list unixODBC-dev <at> mailman.unixodbc.org http://mailman.unixodbc.org/mailman/listinfo/unixodbc-dev(Continue reading)
> > 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 _______________________________________________ unixODBC-dev mailing list unixODBC-dev <at> mailman.unixodbc.org http://mailman.unixodbc.org/mailman/listinfo/unixodbc-dev
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? -- -- Nick > _______________________________________________ > unixODBC-dev mailing list > unixODBC-dev <at> mailman.unixodbc.org > http://mailman.unixodbc.org/mailman/listinfo/unixodbc-dev(Continue reading)
> 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.(Continue reading)
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).(Continue reading)
RSS Feed