The system I'm using now has a database table with the students' names, id numbers, majors, emails, etc. and it is very easy to import a text file with all that info right into the table. When the semester is over I just save the grades to another text file and then clear out the table and import the next semester's roster. I have something like 330 students a semester and I really don't want them all sitting around in my database when it is over.
So it sounds like my first idea was the right one - to use my student database as one of the auth backends, and then just clean it out at the end of each semester, just like I'm doing with the system now. Cool. Thanks for the input guys. Tamara On Sep 10, 2006, at 7:13 PM, James Bennett wrote: > > On 9/10/06, Tamara D. Snyder <[EMAIL PROTECTED]> wrote: >> I'd like to reuse the application next semester, with a different set >> of students. And I naturally don't want my students to have any >> access at all to the admin site. > > The included backend should be sufficient for what you've described. > Users can't log in to the admin unless they have the 'is_staff' flag > set, so that's not a problem. And "expiring" the accounts of past > students is easy enough by toggling their "is_active" bit (which makes > for an easy lambda to pass into 'user_passes_test'). You could even > periodically do cleanup by just deleting everyone whose account is > inactive. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" 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/django-users -~----------~----~----~----~------~----~------~--~---
