I just did a few fetches, no inserts or updates at all. I could reproduce it a several times.
David On 20 čvn, 16:31, mdipierro <[email protected]> wrote: > Did you do > > db.commit() > > after you insert/update via the shell? > The web based shall does not commit transactions automatically because > they may span multiple http requests. If you do not commit them > explicitly the database remains lock. > > I am not sure this is the problem for you but this would cause the > problem you experience. > > Massimo > > On Jun 19, 1:48 pm, David Marko <[email protected]> wrote: > > > > > I just decided today to explore the 'shell' function the web2py > > browser interface offers. But I found it very unstable. This works > > very fine until I want to get back to my app. It locks database access > > that means entire web2py server is locked and must be killed. I know > > the shell interface warns about this and lead me to click on > > 'unlock ...' links, but it doesnt help. I have tried several times > > with the same 'lock' end. My app is connected to PostgreSQL, I run > > latest web2py trunk version on WinXP. The 'shell console' is very > > powerful thing but useless when it causes server freeze. But maybe I > > miss something significant. Can anyone share his experience or maybe > > some hint? > > > David
