On 11 July 2011 21:54, Chris McDonough <[email protected]> wrote: > I don't really know if there's an example of actually storing > permissions, users, and groups in a database somewhere TBH. The > tutorial code stores users and groups in a modle scope global. The task > would be to replace the code that uses that module scope global with > code that uses a database table.
I've just spent the better part of the weekend scouring the docs for some mention or example of how to do auth (both authentication and authorisation) from the database, and gave up and decided to roll my own, because I can't see how to do it from the DB. Which leads me to a question: Why is this so common? Every tutorial I've seen on auth only shows hard-coded groups and permissions, none deal with pulling stuff out of the database. Some don't even bother with dynamic users. I'd bet that 90% of auth implementations use the db, so I'm mystified why I never see an example of it. Not to moan at you guys, I love Pyramid, but it's a deficiency I see in the documentation, and not only in Pyramid. -- Raoul Snyman B.Tech Information Technology (Software Engineering) E-Mail: [email protected] Web: http://www.saturnlaboratories.co.za/ Blog: http://blog.saturnlaboratories.co.za/ Mobile: 082 550 3754 Registered Linux User #333298 (http://counter.li.org) -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
