What you describe here would not work. Tables have to be redefined (at the web2py level) every time you need them. Therefore you must call auth.define_tables() or, as far as web2py is concerned, they do not exist. When you define them at the web2py level, if migrate=False, web2py assumes thay also exist in the DB, if migrate=True it does not assumes that and looks into the .table files.
Back to your original problem: ProgrammingError: relation "auth_user" already exists There are two possibilities: 1) the bla_bla_bale_auth_user.table file is missing or corrupted (but I do not think so) 2) You have a custom auth_user in the wrong place in db.py (or with wrong syntax) and the table gets defined twice. I am pretty sure this is the case but I cannot point to the error if I do not see the code. Massimo On Jan 6, 10:35 am, annet <annet.verm...@gmail.com> wrote: > I tried something else, in the auth_table definition I set > migrate=False and I made the auth.define_tables() statement a comment: > > # auth.define_tables() # creates all needed > tables > > I am now able to expose the default/index function and the functions > that do not require login, however, in the list of available databases > and tables only the auth_user table is listed. The auth_event, auth- > group, auth_membership, auth_permission tables are not listed. > Their .table files are in the databases folder and the PostgreSQL > database contains the respective tables. Why aren't they listed, they > have been defined. So no solution to the problem. > > Kind regards, > > Annet.
-- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web...@googlegroups.com. To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
