I'm currently collecting the data about flat prices. I have size, price, location, price per m2 and date of retrieving the data about flat(sample date). I'm plannig create MySQL database filled with this data, which lead me to questions about appropriate schema.
I have two alternatives at my mind.
- Put everything at one huge table
| FLAT_ID | PRICE | SIZE | PRICE_M2 | LOCATION | SAMPLE_DATE |
- Create two tables. One with size, price, location, price per m2 and second for sample date
| FLAT_ID | PRICE | SIZE | PRICE_M2 | LOCATION | SAMPLE_ID |
| SAMPLE_ID | SAMPLE_DATE |
I'm not sure if dividing the table at such manner may bring some advantage using query. Only clear pros of two tables I saw at assumption that date consumes more memory than sample id, so less consuming of sources. On the other had I don't believe that I will have enough data to make hypothetical date column to impact the results. So not sure if it is worth it?
I want to ask advices about this situation and possible approaches.
EDIT: My goal is create the web applications with visualisations of collecting data. Like change the average price through time, average prices at observed locations. Distributions of prices and sizes and visualize the changing of this characteristic through time.