Right, if you use the 'reference sometable' syntax, that will allow you to
have tables reference something which doesn't exist yet. If you use the
db.othertable format, then the othertable absolutely has to exist.
On Monday, March 25, 2013 7:48:02 AM UTC-7, Cliff Kachinske wrote:
As I
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.
I don't think it's a matter of table definition order. Maybe there aren't
any referenced records in
As I understand it, the table does not have to exist when using the
'reference sometable' syntax. Or anyway that's how it's supposed to work.
I'm not 100% confident in it, though so I always make it a practice to
create the reference tables first.
On Monday, March 25, 2013 6:31:16 AM UTC-4,
Agree with it. According to my practice empty can table can be referenced
and the dropdown list is created by without any item. By defining the
referenced tables first does solve my problem.
在 2013年3月25日星期一UTC+8下午10时48分02秒，Cliff Kachinske写道：
As I understand it, the table does not have to
Hi there,
I've created 7 tables from my app and 2 of them cause error when to be
listed from Appadmin (/appadmin/select/db?query=db.t_leads.id0). Don't
see anything particular in the table definition that may cause the problem.
Any help would be apprecicated.
I think the problem may
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',
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
7 matches
Mail list logo
