[web2py] Re: mysql postgres different behaviors

2011-10-18 Thread Massimo Di Pierro
No. I am still very puzzled that the error you quote is not related to the code you posted. The error is in code executed before your code is executed and it is related to parsing input from form submission. Do you use current.request somewhere? If used improperly could, maybe, cause something like

Re: [web2py] Re: mysql postgres different behaviors

2011-10-18 Thread Manuele
On 18/10/2011 15:59, Manuele wrote: On 18/10/2011 15:24, Massimo Di Pierro wrote: One problem I see is this: try: db io except Exception: On exception you should explicitly rollback try: db io except Exception: db.rollback() interesting point... i'll try and report nothing changes..

Re: [web2py] Re: mysql postgres different behaviors

2011-10-18 Thread Manuele
On 18/10/2011 15:24, Massimo Di Pierro wrote: One problem I see is this: try: db io except Exception: On exception you should explicitly rollback try: db io except Exception: db.rollback() interesting point... i'll try and report I also do not know why you defined m_wind_table = db.T

[web2py] Re: mysql postgres different behaviors

2011-10-18 Thread Massimo Di Pierro
One problem I see is this: try: db io except Exception: On exception you should explicitly rollback try: db io except Exception: db.rollback() I also do not know why you defined m_wind_table = db.Table(db, 'm_wind_10min', base_table, Field(...), ...) instead of m_wind_table = db.define_

Re: [web2py] Re: mysql postgres different behaviors

2011-10-18 Thread Manuele
On 18/10/2011 00:23, Massimo Di Pierro wrote: The code in this traceback has nothing to do with postgresql but is related to reading data from the socket. What is the code that causes the problem? http://pastebin.com/yVJskGww here you can find the two function used. The second one reads the xls

[web2py] Re: mysql postgres different behaviors

2011-10-17 Thread Massimo Di Pierro
The code in this traceback has nothing to do with postgresql but is related to reading data from the socket. What is the code that causes the problem? On Oct 17, 9:30 am, Manuele wrote: > Hi *, > I cannot understand why the same function if run with mysql gives me the > subsequent error while it