I would never recommend splitting auth_user in multiple tables. It just makes everything else more complex. Moreover the roles you describe are not always exclusive and therefore you may end up with duplication of data.
On Thursday, 19 February 2015 10:57:32 UTC-6, Jon M. wrote: > > Peaceful Greetings Web2Py Group! > > In my first glances of practicing and implementing this awesome framework, > came across with some doubts with the *authorization* topic. > > In general database, server and services good practices, hand to hand with > security, What do you think that is the best? (based on experience with > hardcore data transmissions) > > Customize the '*user_table*' so the Auth library can do it's job done, > adding fields and have all almighty admins, mid-admins of certain realms, > and users of the different realms that are in the server, distinguished but > stored in the same '*user_table*' > > Or, split that table, so each one out of 3 can have its own table. > > I'm learning DBs on the way too, sorry if the question level bothers > anyone. Kinda new in production environments... I know that it might be > some answer out there, but I wonder about actual epoch IT solutions and > experiences, having in mind the possible future scenarios. It's kinda scary > to me, but awesome and challenging at the same time. > > Thanks a lot for your attention! :D > > Nice day | afternoon | night! > -- 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 web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
