<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Query-Language on christos gkoros</title>
    <link>https://christosgkoros.com/tags/query-language/</link>
    <description>Recent content in Query-Language on christos gkoros</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 06 Aug 2026 09:00:00 +0300</lastBuildDate>
    <atom:link href="https://christosgkoros.com/tags/query-language/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Every API Invents a Query Language</title>
      <link>https://christosgkoros.com/posts/2026/08/06/every-api-invents-a-query-language/</link>
      <pubDate>Thu, 06 Aug 2026 09:00:00 +0300</pubDate>
      <guid>https://christosgkoros.com/posts/2026/08/06/every-api-invents-a-query-language/</guid>
      <description>The moment it happensYou ship GET /pets. Someone asks to filter by status, so you add ?status=available. Then by species. Then someone wants cats or dogs, and a query string has no way to say &amp;ldquo;or&amp;rdquo;, so you invent something — ?species=cat,dog — and quietly decide that commas mean OR today. Then someone wants pets born after 2020, excluding the adopted ones, and you find yourself designing a grammar inside a query parameter.</description>
    </item>
  </channel>
</rss>
