From e7ae8dc76fb3af016a7b6fcb5df3714d3223b399 Mon Sep 17 00:00:00 2001 From: Jesse Mortenson Date: Thu, 26 Sep 2024 18:02:30 -0500 Subject: [PATCH] Querying data: clarify properties that are sub-entities --- docs/data/query-scraper-output-data.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/data/query-scraper-output-data.md b/docs/data/query-scraper-output-data.md index 2f74232..199a1a8 100644 --- a/docs/data/query-scraper-output-data.md +++ b/docs/data/query-scraper-output-data.md @@ -82,7 +82,8 @@ D DESCRIBE SELECT * FROM read_json('bill_*.json'); ``` You'll notice that related entities like Bill Actions, Bill Sponsorships, etc... are embedded in the data as `STRUCT` -data, usually as a list (`STRUCT(property_a VARCHAR, property_b VARCHAR)[]`). We can drill down into those. +data: `actions`, `sponsorships`, etc.. This is typically structured as a list of `STRUCT` data, which is like a dict +or object (`STRUCT(property_a VARCHAR, property_b VARCHAR)[]`). We can drill down into those. ### Use views to drill into the data