Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

Databases

Christina Hooper
Christina Hooper
1,990 Points
Posted by Christina Hooper
Christina Hooper
1,990 Points

best practices for activity logs

I'm building a site that (ideally) will have traffic one day equal to Kickstarter. The client wants to have logging of a variety of activities performed by users around the site. There will be a lot of data over time, and my clients wants to query on it regularly, so my question... what's the best way to store the data? the same database? a different database? text files?

Quinzie Edmonds
Quinzie Edmonds
12,588 Points

C.R.U.D will allow you to create a front end user-interface that users of the site can log into , then store/query/show the data in a specific format to fit clients needs. The best way in my opinion to store the data is the same database with multiple tables (MYSQL/PHP).

Christina Hooper
Christina Hooper
1,990 Points
Christina Hooper
Christina Hooper
1,990 Points

I already have users logging in taken care of. This site is really similar to Kickstarter. It has users of different levels with different permissions logging in and out doing different things. The site owner wants to have a log that he can review of some of the changes that users are creating. Some of it is for error logging like if a credit card doesn't go through and an error message is generated. Other things are like if someone changes their campaign title or funding goal he wants me to log who made the change, when they made it, what it was before, and what it is now. So it could end up being a fairly massive table.