[web2py] Re: SQL Server question, transactions remaining open

2016-06-30 Thread Jason Solack
Thank you for the replies! I am going to try being more explicit and see if that cleans things up On Wednesday, June 29, 2016 at 5:53:36 PM UTC-4, Dave S wrote: > > > > On Wednesday, June 29, 2016 at 11:59:23 AM UTC-7, Niphlod wrote: >> >> you need to be explicit everywhere if you are not in a w

[web2py] Re: SQL Server question, transactions remaining open

2016-06-29 Thread Dave S
On Wednesday, June 29, 2016 at 11:59:23 AM UTC-7, Niphlod wrote: > > you need to be explicit everywhere if you are not in a web request > environment. > > On Wednesday, June 29, 2016 at 2:57:37 PM UTC+2, Jason Solack wrote: >> >> I am, i am passing db into some modules, do i need to be explicit

[web2py] Re: SQL Server question, transactions remaining open

2016-06-29 Thread Niphlod
you need to be explicit everywhere if you are not in a web request environment. On Wednesday, June 29, 2016 at 2:57:37 PM UTC+2, Jason Solack wrote: > > I am, i am passing db into some modules, do i need to be explicit about > db.commit within modules? > > On Tuesday, June 28, 2016 at 3:22:42 P

[web2py] Re: SQL Server question, transactions remaining open

2016-06-29 Thread Jason Solack
I am, i am passing db into some modules, do i need to be explicit about db.commit within modules? On Tuesday, June 28, 2016 at 3:22:42 PM UTC-4, Niphlod wrote: > > are you explicitely calling db.commit() at the end of your taks ? > > On Tuesday, June 28, 2016 at 6:36:02 PM UTC+2, Jason Solack wro

[web2py] Re: SQL Server question, transactions remaining open

2016-06-28 Thread Niphlod
are you explicitely calling db.commit() at the end of your taks ? On Tuesday, June 28, 2016 at 6:36:02 PM UTC+2, Jason Solack wrote: > > Hello all, i am running an app that utilizes the scheduler and i'm seeing > a lot of open transaction in SQL server with the last sql command being: > > IF @@TR