It gets annoying to just recieve the "Invalid Query" response.flash and not
know why the query was invalid. Was it improperly formatted data, was it
actually a bad query (missing a parenthesis)...
I suggest trapping these exceptions appropriately, giving an error message
that actually is useful. I'm sure more specific exceptions besides
ValueError can be caught.
:line 227 in appadmin/default.py
except ValueError as err:
(rows, nrows) = ([], 0)
response.flash = T('Invalid Query %s' % err)
except:
(rows, nrows) = ([], 0)
response.flash = T('Invalid Query')
-Thadeus
--
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.
