I tried using the web shell interface and found it useful, but quite
buggy, with variables going in and out of scope and an unstable
database connection. Below I have pasted a cleaned up example session:
web2py Shell Version 1.66.2 (2009-08-21 12:13:57)
>>> rows = db(db.test.id == 10).select()
>>> rows
Traceback (most recent call last):
File "<input>", line 1, in <module>
NameError: name 'rows' is not defined
>>> rows
<gluon.sql.Rows object at 0xb79e858c>
>>> rows
Traceback (most recent call last):
File "<input>", line 1, in <module>
NameError: name 'rows' is not defined
>>> rows = db(db.sponsor.scrape == 133392).select()
Traceback (most recent call last):
File "<input>", line 1, in <module>
File "/home/web2py/gluon/sql.py", line 2212, in select
r = response(query)
File "/home/web2py/gluon/sql.py", line 2207, in response
self._db._execute(query)
File "/home/web2py/gluon/sql.py", line 770, in <lambda>
self._execute = lambda *a, **b: self._cursor.execute(*a, **b)
InterfaceError: cursor already closed
Has anyone else experienced these kind of problems?
In case it matters, my web2py instance is hosted with Apache and WSGI
on Webfaction.
Richard
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---
