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', -607, 335544
I think its because its trying to create a table with ID as primary key,
but it does not include NOT NULL in the creation of the table.
this is from the sql.log file:
CREATE TABLE auth_user(
id INTEGER PRIMARY KEY,
first_name VARCHAR(128),
last_name VARCHAR(128),
email VARCHAR(512),
username VARCHAR(128),
passwrd VARCHAR(512),
registration_key VARCHAR(512),
reset_password_key VARCHAR(512),
registration_id VARCHAR(512)
);
firebird will not allow this create statement unless it has NOT NULL added.
On Saturday, November 9, 2013 7:00:13 AM UTC-6, Niphlod wrote:
>
> 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 map a user to a
> unique integer(ish) id.
> Moreover, auth_* tables assure you that you won't continuously hit the
> auth backend once authenticated (sort of a "cached" copy of what is needed
> is written into the database).
>
> You shouldn't have problems with firebird .... what is the exception your
> app raises when trying to create the auth tables ?
>
>
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
