@Brian - Yeah, I do need to pull in those rows at one time. I thought I had provided a workaround by only pulling a few thousand at a time and then combining later. I just got back in town from being gone for about a week. I come back and now the problem I was having before is no longer present. It takes a long time to retrieve the rows, about 20 seconds on the app side versus only a few seconds in SQL Server Express for 50k rows, but it runs (my guess is that the app side has to store the results in memory and that is why it takes so much longer). I have no explanation for why this ever happened. It was indeed returning it as None. Again, I don't know why. I had a print len(test) line right after the statement in question (I had the idea to run the same check myself) and the error happened on the print len(test). The error was something like "len() does not work for type NoneType." Again, I am trying to recreate the error to double-check this but I can not because it now works. What kind of speed times are you getting for pulling in all those rows? You said you were testing between 10k and even up to 1.2 mil. Thanks for all of your help. I am going to continue on and hope it doesn't happen again.
-- 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/groups/opt_out.
