However, it is worth noting that being able to set relationships between your datasets is not the only advantage of SQL databases.
So, to wrap it up, whenever you start writing a program, ask yourself, "Do my data interact with each other"? "Do my data look like a community?" If the answer to those questions is "yes, " you probably need a database.
Setting up relationships will help us to filter data easily (e.g., get all students enrolled in a particular course). By using an SQL database here, we can set up relationships between the different database tables. Therefore, in this example, it would be much better to use a relational database, also known as an SQL database. In our previous example of temperature data, the values were more independent In this second school system example, the data have relationships among them (e.g., teachers teach courses and students take courses). The program should allow the user to filter data, produce PDF documents with the filtered data, etc. Students are enrolled in one or more courses, and teachers teach one or more courses. Now let's suppose you are building a school management GUI program where you want to manage student, course, and teacher data. Both CSV and JSON are flexible and simple data formats, and therefore they would be a good fit for such simple temperature data.
In this example, storing those two daily temperature values on a CSV or JSON file would make sense. Suppose you want to build a program that scrapes two air temperature values daily from a website, stores those data, and generates a plot with the stored values. For example, will you store the data in CSV, JSON, or an SQL database? This post will explain how to choose the correct data structure for your program. Before you code a program, you should think of what structure you will use to store your data.
0 kommentar(er)
