Yes its the point. When you simply switch the definition order to person table first, web2py will raise the same error with company table doesnt exist yet.
David On 11 lis, 17:05, DenesL <denes1...@yahoo.ca> wrote: > Some of you have missed Mirek's point, and he has a very valid one. > The problem is circular references. > There are ways around it but no elegant solution yet. > > There was discussion some time ago about lazy evaluation of tables. > > I also would like to see this solved in web2py. > > Denes. > > On Nov 11, 10:36 am, Mirek Zvolský <zvol...@seznam.cz> wrote: > > > > > > > > > >> Here's a link to the section in the book: > > >>http://www.web2py.com/book/default/chapter/06#Self-Reference-and-Aliases > > > Yes, I know this, and from that reason I always use 'reference..' > > style syntax. > > > However this is about very special foreign keys, which targets to same > > table (to the primary key in same table). > > > And if there is some cycle in joins in the model (and of course it > > always is, except of very, very simple models), this will not help. > > And there is realy no solution for this in web2py ??
