[web2py] Re: Code that used to work now fails in 1.74.8 -- Part 2 [SOLVED]

2010-02-01 Thread weheh
Thanks, that did the trick. All fixed. On Feb 1, 12:33 am, mdipierro wrote: > yes, same problem as above. > > On Jan 31, 10:29 pm, weheh wrote: > > > > > After I dropped the assignment__tmp column, I still got a ticket from > > web2py and this time it's complaining about a duplicate column name

[web2py] Re: Code that used to work now fails in 1.74.8 -- Part 2

2010-01-31 Thread mdipierro
yes, same problem as above. On Jan 31, 10:29 pm, weheh wrote: > After I dropped the assignment__tmp column, I still got a ticket from > web2py and this time it's complaining about a duplicate column name > 'reset_password_key'. But when I look for it in auth_user, I only see > one column by that

[web2py] Re: Code that used to work now fails in 1.74.8 -- Part 2

2010-01-31 Thread weheh
After I dropped the assignment__tmp column, I still got a ticket from web2py and this time it's complaining about a duplicate column name 'reset_password_key'. But when I look for it in auth_user, I only see one column by that name. Should I drop that one, too? -- You received this message becaus

[web2py] Re: Code that used to work now fails in 1.74.8 -- Part 2

2010-01-31 Thread weheh
I see. OK, I can do that, I think. -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web...@googlegroups.com. To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com. For more options

[web2py] Re: Code that used to work now fails in 1.74.8 -- Part 2

2010-01-31 Thread mdipierro
The problem is due to the fact that you have tried to change type before and there are columns in db that are not reflected in web2py table. You need to use SQL to access the db and drop those columns "assignment__tmp" On Jan 31, 3:04 pm, weheh wrote: > Incidentally, I removed the requires from t

[web2py] Re: Code that used to work now fails in 1.74.8 -- Part 2

2010-01-31 Thread weheh
Incidentally, I removed the requires from the Field('assignment' ... ) declaration and I still get the same failure on my server. -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web...@googlegroups.com. To un

[web2py] Re: Code that used to work now fails in 1.74.8 -- Part 2

2010-01-31 Thread weheh
OK. I didn't realize I might be changing type. Here's the field "assignment": db.Field('assignment','string', requires=[ IS_NOT_EMPTY(), IS_IN_DB( db(db.cinst.fp_id==request.vars.fp_id), 'cinst.alphanum_id' ), ] ), I wrote this code a long time

[web2py] Re: Code that used to work now fails in 1.74.8 -- Part 2

2010-01-31 Thread mdipierro
Sorry, I meant unwanted columns: "assignment__tmp". web2py created it while you trying to change the type of field "assignment". You only run into the problem if you attempted to change the type into an incompatible type. On Jan 31, 2:22 pm, weheh wrote: > Yes, it is my intention to move to postg

[web2py] Re: Code that used to work now fails in 1.74.8 -- Part 2

2010-01-31 Thread weheh
Yes, it is my intention to move to postgresql. Unfortunately, I have a lot of legacy data on mySQL that keeps me there for the time being. I don't think it's practical for me to change right at this moment. I'm not sure I know what you're recommending? I have no unwanted tables in my db. At least,

[web2py] Re: Code that used to work now fails in 1.74.8 -- Part 2

2010-01-31 Thread mdipierro
This is known (rare) problem with mysql. Mysql cannot perform multiple alter tables in one transactions. It needs to be committed at each alter table. So it may happens that when you try con change type of a file between incompatible types, it fails in between and some of the temp steps have alread