PHP - Moved: Database Design

This topic has been moved to Application Design.

http://www.phpfreaks.com/forums/index.php?topic=327717.0

Okay, not sure what exactly I need but I need to store data in a MySQL database.

The financial data for each user has to be stored for each day.

I.e. User 1 has 20 financial data columns say (rent, maintenance, wages, shopping... etc). I need to store each of those separately so they can be displayed in a report.

There is more than one user. Most likely a couple of hundred users although it needs to work for up to a few thousand users.

Also, each user's daily financial data has to be stored against the date of that data so the user can see the change in finances between day X and day Y for example.

So far my best idea has been to create a table for each user and then in that table store the financial data in the columns against the date as the primary key. Does anyone have a better way for this or should I do this?

I have designed a database for my institute. Here I have attached my design for better understanding.   I am expecting your reviews who are professional for the database design.   Thank You.     Attached Files  Database Design for Institute Registration.jpg   61.29KB   0 downloads

This is a more general schema design question as opposed to specific queries.   I'm designing a database which tracks the production status of 2 (and in the future maybe 2 or so more) completely different products. So let's call these products productA and productB. I have a page where the user can see the progress of either of the products.   This concerns these 3 tables:   productA(id, order_id, status) productB(id, order_id, status) production_status(id, status, ordering, type)   The status is number based PER product so that it can move up a chain of statusses in its production process. So if a product is in status with ordering 10 it's done (assuming there are 10 production steps). So at ordering 1 its production just started. The status field contains at which production step it is which will be visible on the page. Now this is where i get stuck. I somehow have to differentiate between statusses so I know which statusses belong to which product. I put type in so it could filter for either productA or productB, but also for future products. But working with strings is not such a smart idea I think. I could make 2 more seperate tables, but I'm not sure how well that would scale.   So my question is what a good approach would be.   Some background info: I'm building a Joomla component for a small company. Like I said they want to track the status of these products. Every time a production person unpublishes said item on its production view inside the component, the product moves to the next status
Edited by Ortix, 13 May 2014 - 04:14 AM.

I have spent lots of time trying to design a nice structure for my project and I would like some feedback to what you guys think, please note this is the first time I've ever done anything like this.   About My Project I am creating a service where advertisers can search through a catalog of websites they want to directly advertise on. Once they have found a website, they can upload an image, pay the fees and start advertising on that website instantly.   I have designed an image of how I think the structure should look, I have designed it this way for efficiency but I am pretty sure I could improve with some help. If you need more info or have any questions, please ask.   Project Structure Design Image   Thanks for reading, what do you think about this structure? Can I improve it?
Edited by itsliamoco, 26 July 2014 - 09:34 PM.