[web2py] Re: datetime and represent

2010-03-28 Thread mdipierro
If you run from source you can upgrade from google. Or email me your ip. On Mar 28, 7:08 pm, Avik Basu wrote: > I'm still way back on 1.75.4, but can't upgrade because my IP seems to > be blocked from accessing web2py.com. > Avik > > On Mar 28, 7:32 pm, mdipierro wrote: > > > I see. I think what

[web2py] Re: datetime and represent

2010-03-28 Thread Avik Basu
I'm still way back on 1.75.4, but can't upgrade because my IP seems to be blocked from accessing web2py.com. Avik On Mar 28, 7:32 pm, mdipierro wrote: > I see. I think what you are seeing is due to a bug. I have fixed this > bug but I do not recall if it is fixed in only in trunk or also in > 1.7

[web2py] Re: datetime and represent

2010-03-28 Thread mdipierro
I see. I think what you are seeing is due to a bug. I have fixed this bug but I do not recall if it is fixed in only in trunk or also in 1.76.5. Which web2py version do you use? Massimo On Mar 28, 6:18 pm, Avik Basu wrote: > I dropped all the records in the table and still get the same result. >

[web2py] Re: datetime and represent

2010-03-28 Thread Avik Basu
I dropped all the records in the table and still get the same result. I replaced the previous represent with: represent = lambda x: type(x) which shows that the records are in fact of type datetime as opposed to string. could the issue be in the rendering of tables in appadmin? Avik On Mar 28,

[web2py] Re: datetime and represent

2010-03-28 Thread mdipierro
It is possible you chaged the type of this field from 'string' to 'datetime' and because sqlite does not support migrations, you may have still string data in the datetime field. I suggest you delete those records that contain corrupted data. Massimo On Mar 28, 4:54 pm, Avik Basu wrote: > I woul