Problem is that database is closed when the page returns (and rolled back) so any attempt to use db will result in "database closed". This is the hard part.
On Mar 9, 10:33 am, Jon Romero <[email protected]> wrote: > On Mar 9, 6:28 pm, mdipierro <[email protected]> wrote: > > > Let me think about this. > > We could: > > 1) save the response._environment in ram > > 2) if logged in user is admin allow the user to open a web2py shell in > > the above environment. > > Yes! > > > the main problem is what do we do with database transactions? when do > > we close them? > > Whatever happened before the "crush", should be stored (db.commit()). > After that, it's like the normal web2py shell (user has to commit by > himself). > > > > > Massimo > > > On Mar 9, 10:17 am, Jon Romero <[email protected]> wrote: > > > > I've seen that Pylons has an AWESOME debugger. > > > Every time an error occurs, you have an AJAX console where you can > > > inspect elements! > > > > This is waaaaaaay more useful than tickets (at least on development) > > > where you click a ticket, go to the new page, read the error, do a > > > print in your code so you can inspect the element, close the ticket > > > page and refresh to get a new ticket, go to the error page, watch the > > > error etc etc ... > > > > How difficult is to add something like this in to web2py? -- 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.
