well, they shouldn't but that's a VPS you're on.... who knows what kind of kinky storage is running under it... web2py raises that error if it can't un-pickle .table files...so it's not properly a web2py issue, more of a problem with that file being somewhat "tampered with". web2py writes to the file only if a table definition is altered...but for auth_cas table the definition is static, so in theory, web2py writes to it ONLY if it doesn't exist in the first place (i.e. the very first request for that app). However, it reads from it every time a request comes in if migrations are turned on, hence the error you were seeing, but not due to web2py, due mostly to the underlying filesystem being "not so consistent".
On Saturday, May 3, 2014 7:13:58 PM UTC+2, peter wrote: > > I thought that leaving migrations on only affected performance? How can it > cause corruptions? > i.e you are right I have left them on. > > Thanks > Peter > > -- 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/d/optout.
