Shouldn't parent be "reference page", not integer, and not have a default value at all?

Anyway it does seem like a DAL bug since page is indeed defined.

same here!
upgrading from 2.12.3 to 2.14.3 broke compatibility with my application.
Tried all versions so found out that last good versions was 2.13.4 and first broken is 2.14.1

My exact error:
AttributeError: 'DAL' object has no attribute 'trunks'

my relevant db.py sections:

db  = DAL('mysql://user:password@192.168.1.111/dbname',  pool_size=myconf.take('db.pool_size', cast=int), check_reserved=['mysql'],lazy_tables = True,
db.define_table('sedi',
                Field('name',            length=100, requires=IS_NOT_EMPTY()),
                Field('dominio',         'reference domini', writable=False, readable=False, default=lambda:session.domain ),
                Field('dipartimento',    'reference dipartimenti'),
                Field('trunk',           'reference trunks', ondelete='SET NULL', requires=IS_EMPTY_OR(IS_IN_DB(db, 'trunks.id','%(id)s - %(name)s'))),
                format='%(name)s',
                common_filter = lambda query: db.sedi.dominio==session.domain,
                )
db.define_table('trunks',
                Field('dominio',            'reference domini', writable=False, readable=False, default=lambda:session.domain ),
                Field('name',               length = 100, requires=IS_NOT_EMPTY()),
                Field('enabled',            'boolean', default = False),
                format='%(name)s',
                common_filter = lambda query: db.trunks.dominio == session.domain,
                )

Tried to isolate the problematic file.
Seems to be gluon/validators.py
Butsyk, try to downgrade just that file with the 2.13.4 version one.

trunks should maybe come before sedi??

On Tue, Apr 12, 2016 at 9:04 AM, Marvi notifications@github.com wrote:

same here!
upgrading from 2.12.3 to 2.14.3 broke compatibility with my application.
Tried all versions so found out that last good versions was 2.13.4 and
first broken is 2.14.1

My exact error:
AttributeError: 'DAL' object has no attribute 'trunks'

my relevant db.py sections:

db = DAL('mysql://user:password@192.168.1.111/dbname', pool_size=myconf.take('db.pool_size', cast=int), check_reserved=['mysql'],lazy_tables = True,
db.define_table('sedi',
Field('name', length=100, requires=IS_NOT_EMPTY()),
Field('dominio', 'reference domini', writable=False, readable=False, default=lambda:session.domain ),
Field('dipartimento', 'reference dipartimenti'),
Field('trunk', 'reference trunks', ondelete='SET NULL', requires=IS_EMPTY_OR(IS_IN_DB(db, 'trunks.id','%(id)s - %(name)s'))),
format='%(name)s',
common_filter = lambda query: db.sedi.dominio==session.domain,
)
db.define_table('trunks',
Field('dominio', 'reference domini', writable=False, readable=False, default=lambda:session.domain ),
Field('name', length = 100, requires=IS_NOT_EMPTY()),
Field('enabled', 'boolean', default = False),
format='%(name)s',
common_filter = lambda query: db.trunks.dominio == session.domain,
)

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#1266 (comment)

In this simple case would resolve the problem. But the complete application has many other tables and relations in a way that at least one relation must come before the table that refers to.
With the parameter lazy_tables = True would not be an issue, until version 2.14.1....

Yes apparently IS_IN_DB stopped being lazy when evaluating the field. I'm looking at it, this issue is very easy to reproduce. Just put this pretty commonly used table in your db.py

db.define_table('category',
    Field('parent_id', 'reference category', requires=IS_EMPTY_OR(IS_IN_DB(db, 'category.id', '%(name)s'))),
    Field('name')
)

I think it can come from 2.13.4, I remember having noticed something
strange when try using a old app removing migrate=False... It may come from
earlier version since I use to set migrate=False since a long time...

On Wed, Apr 13, 2016 at 7:41 PM, Leonel Câmara notifications@github.com
wrote:

Yes apparently IS_IN_DB stopped being lazy when evaluating the field. I'm
looking at it, this issue is very easy to reproduce. Just put this pretty
commonly used table in your db.py

db.define_table('category',
Field('parent_id', 'reference category', requires=IS_EMPTY_OR(IS_IN_DB(db, 'category.id', '%(name)s'))),
Field('name')
)

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#1266 (comment)

I have a fix for it, let me just add a test for it to make sure it doesn't happen again.

@butsyk @BMarvi done, thanks for reporting the issue. Here's the pull request with the fix #1293