Kinda like django's stacktraces ?
I have been an advocate for this for a while, yet since I have been
using WingIDE debugger I havn't really needed this.
-Thadeus
On Tue, Mar 9, 2010 at 11:10 AM, Jon Romero wrote:
> I don't think this is a problem.
>
> If I wanted to check the data of db, I
I don't think this is a problem.
If I wanted to check the data of db, I would use a sqlite viewer (or a
mysql viewer). 99% of cases I just want to
check a variable, sessions or vars/args. I don't want to have a full
blown terminal to experiment.
Just a screen where I can poke around, see what is t
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 wrote:
> On Mar 9, 6:28 pm, mdipierro wrote:
>
> > Let me think about this.
> > We could:
> > 1) save the re
On Mar 9, 6:28 pm, mdipierro 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
>
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.
the main problem is what do we do with database transactions? when do
we close them?
Massimo
On Mar 9, 10:17 am, Jon Romero wr
5 matches
Mail list logo
