search

keiththomas1 / Uplift

A depot for the mobile app which is a student project at University of Illinois at Chicago.
0 stars 0 forks source link

Multi-user support #18

Closed erikboyle closed 10 years ago

erikboyle commented 10 years ago

User fields need to be added to the database tables. BusinessTier (and maybe Widget) functions need to be modified accordingly.

Should eventually be linked in with the Login screen by saving the currUserID that can be accessed and passed to every query.

maximusNullus commented 10 years ago

I'll get on this during my spare time on Thanksgiving.

maximusNullus commented 10 years ago

This is next on my worklist.

maximusNullus commented 10 years ago

Working on this. Start working on the Widget side of this one. I'm working in the business tier on this and I am modifying the database structure again:

I'm putting the user_id in exercise_table and workout_table and using inner joins to retrieve this information in the exercise_set_log and the workout_log for each user (we just do a select statement and use a join where exercise_set_log.workout_name_id = workout_table.workout_name_id and user_id = 1 or 2 or 3, etc).

This means that anything that uses the exercise_table or the workout_table is going to require a user_id param each time they are called. I'm trying to get a list of these functions into the commenting.