Edited markdown and SQL files, added Logical Model PDF

[amera6]

What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)

I created a Logical Model for the relationship between two tables: customer_purchases and market_date_info. This model saved as a PDF and was added to the assignments/DC_Cohort folder in the repo as I didn't know where else to put it. I also added my code to the assignment1 SQL file and my reflection answer to the assignment1 markdown file.

What did you learn from the changes you have made?

I learned a lot about querying data in SQL, such as combining tables, aggregating rows through counts or summation, filtering rows based on a set of conditions, etc. This was also the first time I created a diagram for representing the relationship between tables in a dataset, which I'm proud of being able to interpret as I used to find those graphs quite daunting before this course.

Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?

I wanted to include the names of the vendors when counting how many times they rented the booths in the farmers market (section 3 of the assignment), as opposed to just showing the counts and the vendor_id alone. It took some re-arranging and googling to understand how I could join these results to the vendor table so that I could pull out the names.

Were there any challenges? If so, what issue(s) did you face? How did you overcome it?

I had difficulty with the order of the operations in the SQL code. For example, not knowing if I should "group by" or "order by" first, or whether I could select columns from tables that have yet to be joined to my main table. Again, some trial and error alongside web searching helped me out.

How were these changes tested?

I re-ran the selected chunks of code and debugged any errors (for example, vendor_id being ambiguous meant that I needed to explicitly declare which table I want the vendor_id column to be sourced from).

A reference to a related issue in your repository (if applicable)

Checklist

• I can confirm that my changes are working as intended

[anjali-deshpande-hub]

Very well done! 30/30

Thank you for your thoughtful reflection on section 4 - your point on how database design can make it harder to study and address inequalities.