Fixes #16. After discussion with Matt, we decided not to enforce any uniqueness constraint here. This required retrofitting a couple of migrations, but since the code doesn't work for databases that enforce unique constraints prior to this commit, this won't break any existing installs.
Anything that used to be indexed from a language code is now indexed from a Language.id value (sometimes written as Profile.language_pref_id).
Still need to migrate all code that uses this across.
Closes #18. We forgot to make the link from UserProfile -> User be the attribute "user". This fixes that, but the easiest way to migrate between models when changing the primary key is to create a new model and copy the data back and forth. So I've created the Profile model that mirrors the old UserProfile, except that "student" is now called "user".
Closes issue gh-17.
…equirements in the requirements file
We can't do any dash'ing today (day jobs for those of us in regular timezones), so this just updates where we got to.
…n the current words being studied is refreshed.
We just ignore this situation and present the user with a new question.
…r user, added to dynamically, and removed when you get it correct enough times