user row: I have an app with a user row - r._user.keys() ['rating', 'last_name', 'pageviews', 'ip', 'number_polls', 'site', 'myrand', 'hotmail', 'number_activities', 'skype', 'id', 'city', 'rawpassword', 'number_useraudios', 'zip', 'number_votes', 'last_login', 'number_userpics', 'music', 'email', 'number_pages', 'username', 'number_posts', 'hash', 'number_comments', 'number_pictures', 'first_name', 'yahoo', 'groups', 'heroes', 'favoritestuff', 'number_usermessages_sent', 'vanity', 'interests', 'television', 'number_uservideos', 'created', 'dob', 'gender', 'number_friends', 'liketomeet', 'htmlcodes', 'aim', 'movies', 'password', 'books', 'profilepic', 'number_usermessages', 'email_subscribe', 'number_communities']
OK here is the problem, i dont want to keep adding columns to the user table, as it gets too bulky n renders the user table to be efficiently operated I need an extended table to start storing extended information, the problem is the extended table might not be fully filled as the user table, the extended table needs to be sparse with data only for the users who insert the data for eg., users who store their favorite data CREATE TABLE extended( id serial primary key, info1 text, info2 text, info3 text, created timestamp default now(), user_id integer ); user_id links to users.id but extended table has only rows corresponding to users who have entered info1, info2 info3 any thoughts on the best practises on how to manage extended user info thanks a lot --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web.py" 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/webpy?hl=en -~----------~----~----~----~------~----~------~--~---
