So, my boyfriend was reading over this, and he asked me to drop a reply to this, since he doesn't have an LJ account YET (I will force him to make one, one day, haha...):
"This seems like a pretty reasonable spec and you are thinking the same as I am as far as sqlite + Python is concerned. I've never worked with OpenID before (aside from using it to login to things myself) but it seems a reasonable idea.
As far as the database schema goes, I would caution against 1 table per user. Something more like:
One table for users One table for feedback with two foreign keys to the user table (person leaving feedback, person receiving feedback)
That schema is a lot more scalable than creating an entire table for every user in the system.
If you already have an Apache server that can run Django or something I could look into doing this over my vacation with my family in the next two weeks. It sounds like an interesting project."
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
regna
(no subject)
Date: 2011-12-22 05:03 am (UTC)"This seems like a pretty reasonable spec and you are thinking the same as I am as far as sqlite + Python is concerned. I've never worked with OpenID before (aside from using it to login to things myself) but it seems a reasonable idea.
As far as the database schema goes, I would caution against 1 table per user. Something more like:
One table for users
One table for feedback with two foreign keys to the user table (person leaving feedback, person receiving feedback)
That schema is a lot more scalable than creating an entire table for every user in the system.
If you already have an Apache server that can run Django or something I could look into doing this over my vacation with my family in the next two weeks. It sounds like an interesting project."