thecard Posted November 22, 2009 Share Posted November 22, 2009 I have a standard table full of users, there are a few fields: id, user, pass, email... These are filled in when a user registers/changes personal information. What I need is to work out the most elegant way that I can store the "personal" information of each user everyday at a certain time. This is so that I can then submit a query for instance to find out what a user's password was on the 16th of November 2009 or what his/her email address was 100 days ago. Thanks for ANY help. I really just can't get my head around it. Quote Link to comment Share on other sites More sharing options...
fenway Posted November 25, 2009 Share Posted November 25, 2009 Why? Quote Link to comment Share on other sites More sharing options...
thecard Posted November 25, 2009 Author Share Posted November 25, 2009 Because I am coding a site which needs to have detailed graphs of user data over time periods. The user will see information about their account written on graphs. Quote Link to comment Share on other sites More sharing options...
fenway Posted November 25, 2009 Share Posted November 25, 2009 hard to graph text, but sure. You simply need to duplicate your records instead of overwriting them. Quote Link to comment Share on other sites More sharing options...
salathe Posted November 25, 2009 Share Posted November 25, 2009 Why on earth would you need to know what a user's password is now, let alone all of their previous ones? Quote Link to comment Share on other sites More sharing options...
thecard Posted November 25, 2009 Author Share Posted November 25, 2009 Right. I'm sorry. I shouldn't have used the example of passwords. I don't want to know my users' passwords EVER. I'm sorry! What I should have stated is that on the website there is a point system: I need to record the number of points each user has on every single day. What is the best way of laying out my database to do this? Do I have a table for points then have a field called "date"? Pretend I didn't make the other post, I must have been mental at the time. Quote Link to comment Share on other sites More sharing options...
fenway Posted November 25, 2009 Share Posted November 25, 2009 Like I said earlier, just dupe the record. Quote Link to comment Share on other sites More sharing options...
thecard Posted November 25, 2009 Author Share Posted November 25, 2009 Thanks, but is there not a more "efficient" way? Won't that just take up LOADS of tables (one for every day!). Quote Link to comment Share on other sites More sharing options...
fenway Posted November 25, 2009 Share Posted November 25, 2009 Thanks, but is there not a more "efficient" way? Won't that just take up LOADS of tables (one for every day!). Well, if you want that history, you have to store it somewhere. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.