[web2py] Overiding the auth table ID fields to allow for release over pillars (Development, Acceptance, Production)

why do you have to override ids? You can just create users with the required ids. -- 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

[web2py] Overiding the auth table ID fields to allow for release over pillars (Development, Acceptance, Production)

We are planning on using Web2Py in a 3 tier release model (Development, Acceptance, Production) but as the ID fields in the auth tables are used as primary and foreign keys, we are concerned that this will cause inconsistencies between the different pillars. We will be using SSO for access to