{
  "video_id": "reddit_1vxud0f",
  "channel_slug": "programming",
  "channel_handle": "r/programming",
  "title": "Solving the 1+N Query Problem",
  "url": "https://www.reddit.com/r/programming/comments/1vxud0f/solving_the_1n_query_problem/",
  "external_url": "https://acadia.engineering/blog/solving-the-1-plus-N-query-problem",
  "upload_date": "20260825",
  "published_at": "2026-08-25T08:56:56+00:00",
  "transcript": "\n\n--- Top Comments ---\n\n\n[30 upvotes] There is a really easy way of avoiding this when you just don't use ORMs \n\n[28 upvotes] ive been using EF Core for ORM and this hasn't really been a problem for me or any of my colleagues for at least a decade because we don't use lazy loading. database calls are explicit; mapping the results to objects is implicit. is everyone outside of .net still banging their heads against stuff like this?\n\n[23 upvotes] I don't know why people hate on ORMs for this one, yes abstracting SQL can lead some devs to forget / not even know about what is actually happening under the hood, but it isn't that big of a deal! \n\nMake sure your dev team is aware of the JOIN concept and you're good to go!",
  "transcript_chars": 724,
  "ingested_at": "2026-08-25T13:30:17.882456+00:00",
  "source": "reddit",
  "yt_meta": {
    "score": 51,
    "upvote_ratio": 0.83,
    "num_comments": 40,
    "author": "wheatBread",
    "is_self": false
  }
}