<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Activerecord on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/activerecord/</link>
    <description>Recent content in Activerecord on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 30 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/activerecord/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Ruby ORM Libraries Compared: ActiveRecord vs Sequel vs ROM-rb</title>
      <link>https://www.pistack.xyz/posts/2026-07-30-ruby-orm-libraries-activerecord-sequel-rom-rb/</link>
      <pubDate>Thu, 30 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-07-30-ruby-orm-libraries-activerecord-sequel-rom-rb/</guid>
      <description>&lt;p&gt;Object-Relational Mapping (ORM) is the backbone of most Ruby web applications — it translates between your Ruby objects and relational database tables, handling everything from query generation to schema migrations. While Rails&amp;rsquo; ActiveRecord dominates the Ruby ORM landscape by virtue of being Rails&amp;rsquo; default, two powerful alternatives — &lt;strong&gt;Sequel&lt;/strong&gt; and &lt;strong&gt;ROM-rb&lt;/strong&gt; — offer fundamentally different philosophies that may better suit certain projects.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
