... so you find the default db.py comments ("Define your tables below") not
clear enough, is that correct?
Would changing the default (welcome) db.py to look like something like this
help:
#####################---< your tables section
>---############################
## Define your tables below, for example
##
## >>> db.define_table('mytable',SQLField('myfield','string'))
....
########################################################################
# your table definitions (define before the Auth Section) #
##
#################---< END your tables section
>--############################
#####################-- Auth Section --################################
## Here is sample code if you need:
## - email capabilities
.....
On Fri, Mar 20, 2009 at 2:54 PM, Fran <[email protected]> wrote:
>
> This definition includes:
> db.auth_permission.table_name.requires = IS_IN_SET(db.tables)
>
> Problem is that db.tables is evaluated when the Auth class is
> instantiated
> => only contains those tables created up to that point in the model
>
> Workaround is to explictly call that line at the end of the model(s).
>
> Not sure how to fix the class definition to avoid this.
>
> If we can't then we should update documentation.
>
> F
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"web2py Web Framework" 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
-~----------~----~----~----~------~----~------~--~---
