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 ago, and it doesn't look right. The
requires is mal-formed IMHO. I removed the requires, but I still get
the same duplicate column name error.
There is no reason for me attempting to change the type of
"assignment" to anything other than "string". Some of the
alphanum_id's can be numbers, but I intend them to be interpreted as
strings. Is there some kind of automatic conversion taking place that
I'm unaware of? What should I be looking for to find this problem?
On Jan 31, 3:24 pm, mdipierro <[email protected]> wrote:
> 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 <[email protected]> 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 [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/web2py?hl=en.
