diff --git a/02_activities/assignments/DC_Cohort/Assignment1.md b/02_activities/assignments/DC_Cohort/Assignment1.md index d5ff55ce4..51375c0d8 100644 --- a/02_activities/assignments/DC_Cohort/Assignment1.md +++ b/02_activities/assignments/DC_Cohort/Assignment1.md @@ -210,4 +210,11 @@ Consider, for example, concepts of fariness, inequality, social structures, marg ``` Your thoughts... + +This was a super interesting article to read! + +My immediate thoughts were about my country of citizenship's equivalent database, "e-devlet" or "e-government" in Turkiye. This website provides access to any and all information on Turkish citizens as linked to their ID number, including health documents (even blood test results are linked!), education history, travel history, police checks, job history, one's entire documented genetic lineage, and so on and so forth. In the past there have been multiple alleged hacks into this system, with third parties accessing citizens' data (allegedly). This touches more on the privacy concern aspects of the system, which is a whole other can of worms. From a more social perspective, this database also is intertwined with strict and sometimes not immediately noticable values systems. For example, Turkish men must complete mandatory military service, and this information is accessible through the e-government database. It is therefore also accessible by any government agency/institution/officer with access to an individual's ID number and the necessary data access. So, for example, if a person forgot to prove their student status in another country (in which case military service is delayed) then he could be logged as evading service. Then, if he went to cross the border at the airport, or got involved in a street mugging and had to go to the police station etc., then he would immediately be arrested and signed up for military service because all his data is linked together and visible. This illustrates a way in which governmental data structures can be used to enforce values systems, which is a problem as we know data systems inevitably have faults, such as simply missing some information. + +This article also made me think of citizenship rights, and who is able to have access to them. If data structures are positioned as the agents which determine who gets to have citizenship rights, cases such as Riz's are bound to occur.These are in fact human decisions being carried out by computers. By de-personalizing human values onto computers, the human agent which could be held accountable if they existed, is removed from the equation. To me, it seems like a good way to go about making it even more difficult to discern who the deciding entity on these cases is, which makes it hard to keep it/them accountable. Much to think about! + ``` diff --git a/02_activities/assignments/DC_Cohort/assignment1.sql b/02_activities/assignments/DC_Cohort/assignment1.sql index a80923591..df4d1c27a 100644 --- a/02_activities/assignments/DC_Cohort/assignment1.sql +++ b/02_activities/assignments/DC_Cohort/assignment1.sql @@ -7,7 +7,8 @@ /* 1. Write a query that returns everything in the customer table. */ --QUERY 1 - +SELECT * +FROM customer; --END QUERY @@ -17,7 +18,10 @@ sorted by customer_last_name, then customer_first_ name. */ --QUERY 2 - +SELECT * +FROM customer +ORDER BY customer_last_name, customer_first_name +LIMIT 10; --END QUERY @@ -28,7 +32,10 @@ sorted by customer_last_name, then customer_first_ name. */ Limit to 25 rows of output. */ --QUERY 3 - +SELECT * +FROM customer_purchases +WHERE product_id IN (4, 9) +LIMIT 25; --END QUERY @@ -43,7 +50,10 @@ Limit to 25 rows of output. */ --QUERY 4 - +SELECT *, quantity * cost_per_quantity AS price +FROM customer_purchases +WHERE customer_id BETWEEN 8 AND 10 +LIMIT 25; --END QUERY @@ -56,7 +66,13 @@ columns and add a column called prod_qty_type_condensed that displays the word if the product_qty_type is “unit,” and otherwise displays the word “bulk.” */ --QUERY 5 - +SELECT + product_id, + product_name, + CASE WHEN product_qty_type = 'unit' THEN 'unit' + ELSE 'bulk' + END AS prod_qty_type_condensed +FROM product; --END QUERY @@ -67,7 +83,16 @@ add a column to the previous query called pepper_flag that outputs a 1 if the pr contains the word “pepper” (regardless of capitalization), and otherwise outputs 0. */ --QUERY 6 - +SELECT + product_id, + product_name, + CASE WHEN product_qty_type = 'unit' THEN 'unit' + ELSE 'bulk' + END AS prod_qty_type_condensed, + CASE WHEN LOWER(product_name) LIKE '%pepper%' THEN 1 + ELSE 0 + END AS pepper_flag +FROM product; --END QUERY @@ -79,7 +104,12 @@ vendor_id field they both have in common, and sorts the result by market_date, t Limit to 24 rows of output. */ --QUERY 7 - +SELECT * +FROM vendor as v +INNER JOIN vendor_booth_assignments AS vba + ON v.vendor_id = vba.vendor_id +ORDER BY vba.market_date, v.vendor_name +LIMIT 24; --END QUERY @@ -93,7 +123,9 @@ Limit to 24 rows of output. */ at the farmer’s market by counting the vendor booth assignments per vendor_id. */ --QUERY 8 - +SELECT vendor_id, COUNT(*) AS booth_rentals +FROM vendor_booth_assignments +GROUP BY vendor_id --END QUERY @@ -106,7 +138,17 @@ of customers for them to give stickers to, sorted by last name, then first name. HINT: This query requires you to join two tables, use an aggregate function, and use the HAVING keyword. */ --QUERY 9 - +SELECT + c.customer_id, + c.customer_first_name, + c.customer_last_name, + SUM(cp.quantity * cp.cost_per_quantity) AS total_spent +FROM customer AS c +INNER JOIN customer_purchases AS cp + ON c.customer_id = cp.customer_id +GROUP BY c.customer_id, c.customer_first_name, c.customer_last_name +HAVING SUM(cp.quantity * cp.cost_per_quantity) > 2000 +ORDER BY c.customer_last_name, c.customer_first_name; --END QUERY @@ -125,6 +167,15 @@ VALUES(col1,col2,col3,col4,col5) */ --QUERY 10 +DROP TABLE IF EXISTS temp.new_vendor; + +CREATE TABLE temp.new_vendor AS +SELECT * FROM vendor; + +INSERT INTO temp.new_vendor + (vendor_id, vendor_name, vendor_type, vendor_owner_first_name, vendor_owner_last_name) +VALUES + (10, 'Thomass Superfood Store', 'Fresh Focused', 'Thomas', 'Rosenthal'); @@ -139,7 +190,12 @@ and year are! Limit to 25 rows of output. */ --QUERY 11 - +SELECT + customer_id, + STRFTIME('%m', market_date) AS month, + STRFTIME('%Y', market_date) AS year +FROM customer_purchases +LIMIT 25; --END QUERY @@ -153,7 +209,13 @@ but remember, STRFTIME returns a STRING for your WHERE statement... AND be sure you remove the LIMIT from the previous query before aggregating!! */ --QUERY 12 - +SELECT + customer_id, + SUM(quantity * cost_per_quantity) AS total_spent +FROM customer_purchases +WHERE STRFTIME('%m', market_date) = '04' + AND STRFTIME('%Y', market_date) = '2022' +GROUP BY customer_id; --END QUERY diff --git a/dsi-sql-a1-logical-model.png b/dsi-sql-a1-logical-model.png new file mode 100644 index 000000000..90b01f12c Binary files /dev/null and b/dsi-sql-a1-logical-model.png differ diff --git a/farmersmarket.db b/farmersmarket.db new file mode 100644 index 000000000..f192df482 Binary files /dev/null and b/farmersmarket.db differ