[web2py] Re: Form stopped working...

2018-02-22 Thread Dave S
On Thursday, February 22, 2018 at 2:54:21 AM UTC-8, Leonel Câmara wrote: > > Well since you already ruined that column. I would go with the lowercase > version of the field as I don't think it's a good practice to use uppercase > in field names. Then remember to check all your code for db.table

[web2py] Re: Form stopped working...

2018-02-22 Thread Dave S
On Thursday, February 22, 2018 at 2:54:21 AM UTC-8, Leonel Câmara wrote: > > Well since you already ruined that column. I would go with the lowercase > version of the field as I don't think it's a good practice to use uppercase > in field names. Then remember to check all your code for db.table

[web2py] Re: Form stopped working...

2018-02-22 Thread Leonel Câmara
Well since you already ruined that column. I would go with the lowercase version of the field as I don't think it's a good practice to use uppercase in field names. Then remember to check all your code for db.table.Website references and change them to db.table.website it should work after that.

[web2py] Re: Form stopped working...

2018-02-21 Thread Joe
Thanks Leonel, what is the best way to fix this problem? I am on Pythonanywhere, I am not sure about what I should do at this point. On Wednesday, February 21, 2018 at 11:31:46 PM UTC+8, Leonel Câmara wrote: > > From the point of view of web2py if you had migrations enabled what > happened was t

[web2py] Re: Form stopped working...

2018-02-21 Thread Leonel Câmara
>From the point of view of web2py if you had migrations enabled was that you deleted the "Website" column in the table and then added a "website" column. When you changed it back, what you did was delete the column "website" and make a new one "Website". The Form is probably working but, if