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 <richard_gor...@verizon.net> wrote: > 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, not that I'm aware of. > > Also, isn't it strange that this is not an issue on my development > platform but it is on my server? (I backed up the data on my server > and put it on my development machine to test this out.) > > If I remove the table, do I move it back in later? Would my data be > lost (obviously unacceptable solution)? -- 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, visit this group at http://groups.google.com/group/web2py?hl=en.
