<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Mariadb on Bootstrapping.org</title>
    <link>https://bootstrapping.org/tags/mariadb/</link>
    <description>Recent content in Mariadb on Bootstrapping.org</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 02 Nov 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://bootstrapping.org/tags/mariadb/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Bootstrapping Now Runs on MySQL and MariaDB and Posts Seed Plans on Pull Requests</title>
      <link>https://bootstrapping.org/bootstrapping-now-runs-on-mysql-and-mariadb-and-posts-seed-plans-on-pull-requests/</link>
      <pubDate>Mon, 02 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://bootstrapping.org/bootstrapping-now-runs-on-mysql-and-mariadb-and-posts-seed-plans-on-pull-requests/</guid>
      <description>&lt;p&gt;Bootstrapping 0.3 is out. It now runs on MySQL 8.0 and later and MariaDB 10.6 and later, as well as SQLite and PostgreSQL. A reference can name its row by several columns. And the repository is now a GitHub Action that posts the seed plan on a pull request and fails the check when a conflict would block the apply.&lt;/p&gt;&#xA;&lt;p&gt;Most Rails, Laravel and Django applications with reference data run on MySQL or MariaDB, so they were the next databases to support. The seed files don&amp;rsquo;t change. Give &lt;code&gt;-db&lt;/code&gt; a URL and the same &lt;code&gt;plan&lt;/code&gt;, &lt;code&gt;apply&lt;/code&gt;, &lt;code&gt;explain&lt;/code&gt; and &lt;code&gt;history&lt;/code&gt; work there:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
