We have looked in this further, and due to the autoincremented ID fields in
the Auth tables, we are going to have a very complicated release process.
The problem is that the ID will be used in all references to the users and
groups but between pillars (DEV,ACC,PRO) the ID's may not be the same
Thanks for your reply.
Maybe override was not the best term. We can create the users using the
userid and groupid as the ids in the user, group and membership tables, but
as Web2Py out of the box creates an id (sequentially incremented) we are
concerned that specifying a different id might
2 matches
Mail list logo
