[web2py] Re: iterselect() and doing other DB actions - Connection is busy with results for another command

2018-01-10 Thread Brian M
Yes, I thought of a different DAL instance but for my situation it isn't really necessary since I can move when I do the commit() or just store that data elsewhere (the commit was really just to store a "I made it through this datetime" checkpoint record). I was more mentioning it for the next

[web2py] Re: iterselect() and doing other DB actions - Connection is busy with results for another command

2018-01-10 Thread Anthony
On Wednesday, January 10, 2018 at 2:48:34 PM UTC-5, Brian M wrote: > > Thank you Anthony, that works! > > Only issue is that while using iterselect() you apparently can't do your > own db.commit() or else you'll get "Function sequence error (0) (SQLFetch)" > I suspect that it may be closing the

[web2py] Re: iterselect() and doing other DB actions - Connection is busy with results for another command

2018-01-10 Thread Brian M
Thank you Anthony, that works! Only issue is that while using iterselect() you apparently can't do your own db.commit() or else you'll get "Function sequence error (0) (SQLFetch)" I suspect that it may be closing the result set that your'e trying to iterate over. :\ On Wednesday, January

[web2py] Re: iterselect() and doing other DB actions - Connection is busy with results for another command

2018-01-10 Thread Anthony
Have you tried enabling the Multiple Active Result Sets option? I think you can do so by adding the following to the connection string: DAL('mssql4://username:password@localhost/test?MARS_Connection=yes', ...) Note, it may need to be all caps -- MARS_CONNECTION. Anthony On Wednesday, January