To follow up on the last entry , what I amusing Django for is (re)writing our account request handling system.The simple version of how people get accounts here is a three stepprocess. The would-be user tells us at least their desired Unix login,their name, their email address, and which professor is sponsoringthem. We ask the professor if they actually want to sponsor the person'saccount; if the professor says yes, we create the account and email therequester with details

I've finally gotten to do something with Django , and naturally this has left mewrestling with schema design. This is the first time I've used an ORMand I find that I'm being pulled two ways, neither of which I thinkare right.

(I'll pause here to note that the data I have to keep track of inthis application is tiny, on the order of a few hundred rows intotal. I'm using Django's ORM support because this gives me