I think I kinda figured out the problem. The order of defining tables seems
matter. Tables to be referenced need to be defined before the referencing
tables. Guess it's a rookie mistake.
Spring
在 2013年3月25日星期一UTC+8上午9时13分56秒，Spring写道：
>
> Hello Alan,
>
> Thanks for the reply. I noticed the common thing of the two error tables
> is that they're both referenced by some other tables while do not reference
> to any. Showing one of referencing table:
>
> db.define_table('t_clients_in',
> Field('f_account_id', type='reference t_accounts',
> label=T('Account ID')),
> Field('f_lead_id', type='reference t_leads',
> label=T('Lead ID')),
> Field('f_status', type='string',
> label=T('Involvement Status')),
> Field('f_sow', type='string',
> label=T('Scope of Work')),
> Field('f_needs', type='list:string',
> label=T('Needs')),
> # Field('f_last_update', type='datetime',
> # label=T('Last Update')),
> Field('f_remarks', type='list:string',
> label=T('Remarks')),
> auth.signature,
> format='%(f_account_id)s',
> migrate=settings.migrate)
>
> I'm not sure if the table reference was used correctly in field definition.
> Now I hashed out all datetime field definition because I found there was
> two fields of "modified_on" and "created_on" which i have no idea where
> they're from since I didn't define them...
>
> One more question here is, for the above table "t_clients_in", the first
> two fields "f_account_id" and "f_lead_id" refer to another two tables
> respectively. When use "new record" in Appadmin, "f_account_id" is a
> fill-in while "f_lead_id" becomes a dropdown (which is good). I cannot see
> where the difference comes from.
>
> Thanks in advance.
>
> Spring
>
>
>
>
>
>
>
>
>> I think the problem may not be about the table definitions, but about the
>> data that DAL is trying to retrieve for the datetime type fields. Are you
>> reading a database from another application?
>>
>> I'd check that the values stored for the datetime fields have the proper
>> format.
>>
>>
--
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
