<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Releases on HyperCrux.com</title>
    <link>https://hypercrux.com/tags/releases/</link>
    <description>Recent content in Releases on HyperCrux.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 06 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://hypercrux.com/tags/releases/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>One SQLite File Instead of Three Databases: HyperCrux 0.1 Keeps Records, Links and Vectors Together</title>
      <link>https://hypercrux.com/one-sqlite-file-instead-of-three-databases-hypercrux-0.1-keeps-records-links-and-vectors-together/</link>
      <pubDate>Tue, 06 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://hypercrux.com/one-sqlite-file-instead-of-three-databases-hypercrux-0.1-keeps-records-links-and-vectors-together/</guid>
      <description>&lt;p&gt;Add search by meaning to an app and the data splits in three. The records stay in the regular database. Their embeddings go to a vector database, so the app can find documents that are about the same thing as a question. The connections between records, who owns what and which document cites which, end up in a graph database or a join table nobody likes. Then something has to copy every change from one to the others, and the day it misses one, a search returns a document that was deleted last week.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
