that is something that backends don't report, so there's no way for web2py to know, except that IT IS happening (but no ETA)
I NEVER use web2py to trigger migrations in productions. there's sql.log on the developer machine for that. On Friday, July 4, 2014 11:00:24 AM UTC+2, Encompass solutions wrote: > > It would be nice if there was some way for us to see a database change > happening. > In my production environment I had a big migration happening, but I didn't > know this and started getting unexpected time outs all the time. > I could get into the admin side and it would have been nice to see that a > database migration call was happening. (And really cool, the percentage > done.) > What do you guys think? > BR, > Jason > -- 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.
