This is not a web2py error. It may be a db error. What db? Can we see complete traceback?
The locked variable is currently not used so in any case should not be of concern. The idea was to lock the db record when the session is accessed by a client. This function is currently disabled. On Feb 15, 12:45 pm, Dmitri Zagidulin <[email protected]> wrote: > I've started seeing the following warning on the logging console: > > /gluon/sql.py:739: Warning: Out of range value adjusted for column > 'locked' at row 1 > self._execute = lambda *a, **b: self._cursor.execute(*a, **b) > > I'm assuming it's related to the sessions table (since I'm keeping my > sessions in db and not on disk), since that's the only column named > 'locked' that I know of. > > Any idea what could be causing it? (I'm running web2py 1.67.2) -- 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.
