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 10, 2018 at 11:16:48 AM UTC-6, Anthony wrote:
>
> 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/mydb?MARS_Connection=yes', ...)
>
> Note, it may need to be all caps -- MARS_CONNECTION.
>
> Anthony
>
> On Wednesday, January 10, 2018 at 10:48:19 AM UTC-5, Brian M wrote:
>>
>> I'm attempting to process through record sets from DAL queries that can
>> sometimes return hundreds of thousands of records. To try to keep memory
>> usage under control I wanted to use iterselect() instead of a plain DAL
>> select(). However, the problem I'm running into is that as I process each
>> record I need to perform other actions against the same database but when I
>> do so I get "Connection is busy with results for another command" because
>> of course I haven't finished getting all of the records yet. Is there some
>> simple way to deal with this? Seems like it'd be the norm to need to do
>> other things with the database while using iterselect().
>>
>> I'm using a Microsoft SQL Server database with pyodbc. The DAL connection
>> is using mssql4n with {SQL Server Native Client 11.0} as an extra driver
>> argument.
>>
>
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
