Ok. If it helps with the troubleshooting, I am getting the error when connecting to SQL Server, not SQLite. Not sure if the problem is db backend-specific, but I thought I'd throw it out there.
Thanks for the quick response. On Fri, Aug 13, 2010 at 10:03 AM, mdipierro <mdipie...@cs.depaul.edu> wrote: > nothing. this is a known bug which we think is related to timeout in > keeping the sqlite connection open. For now use the normal shell. > > On Aug 13, 8:59 am, mwolfe02 <michael.joseph.wo...@gmail.com> wrote: >> I'm trying to run a very simple select query from the built-in web- >> based shell, but I keep getting the following error: The cursor's >> connection has been closed. >> >> Here is the full traceback: >> >> Traceback (most recent call last): >> File "<input>", line 1, in <module> >> File "...\web2py\gluon\sql.py", line 3214, in select >> rows = response(query) >> File "...\web2py\gluon\sql.py", line 3209, in response >> db._execute(query) >> File "...\web2py\gluon\sql.py", line 1087, in <lambda> >> self._execute = lambda *a, **b: self._cursor.execute(*a, **b) >> ProgrammingError: The cursor's connection has been closed. >> >> What am I doing wrong? It would be really hand to debug queries >> interactively. >> >> Thanks, >> Mike
