Niphlod,
Thanks for all your help. We have the app working now. To answer your
questions:
1. yes, password and role are reserved words in Firebird 1.5; Not sure
about 2.x version though
2. I can see uses for rname down the road. Glad its in the works.
3. We're using Firebird 1.5 because
Very strange, since fdb is included as an adapter for some time now. I
guess firebird adoption is definitely not widespread.
This should be addressed in DAL at creation time.
Can you provide the syntax that web2py should use vs the sintax that it
actually uses ? Maybe open a ticket on google
Niphlod,
I manually defined the auth tables. However, system is now saying
auth_user already exist.
class 'fdb.fbcore.DatabaseError' ('Error while executing SQL
statement:\n- SQLCODE: -607\n- unsuccessful metadata update\n- Table
AUTH_USER already exists', -607, 335544351)
Version
web2py™
if password and role are reserved keywords, then there is a huge issue
because what needs to be changed is how auth creates the scheme by default
(and I don't see it happening in web2py for a small percentage of firebird
users)...
One thing at a time though. We need to figure out the problem
web2py definitely needs the auth tables to work with any auth backend (even
LDAP).
Of course username and pwd are stored in AD, but AD doesn't have, e.g, the
user id.
web2py uses auth_* tables for dealing with RBAC, and even if you don't need
granular permissions, groups etc, it still has to
Niphlod,
Thanks for the response. I understand it better now.
web2py generates this message
DatabaseError: ('Error while executing SQL statement:\n- SQLCODE: -607\n-
unsuccessful metadata update\n- Column: ID not defined as NOT NULL - cannot
be used in PRIMARY KEY constraint definition',
6 matches
Mail list logo
