This probably means you do something in the model that breaks the transaction. It is a coding error. You may want to look in the postgresql for the exact problem. It is a postgresql error, not a web2py error.
On Oct 14, 3:39 am, Manuele Pesenti <[email protected]> wrote: > Hi *, > I'm a new web2py user and I got this error for the second time: > > InternalError: current transaction is aborted, commands ignored until > end of transaction block > > The problem is that this error still appear even after restoring the > source code and restarting the web2py server > > the first time I by-pass this creating a new better constructed project > with a new db (postgres), but is there a way to resolve it in a better way? > > Thanks a lot > > Manuele
